Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document for "How to track performance issues" #59

Open
cnrpman opened this issue Jan 11, 2023 · 0 comments
Open

Document for "How to track performance issues" #59

cnrpman opened this issue Jan 11, 2023 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@cnrpman
Copy link
Collaborator

cnrpman commented Jan 11, 2023

It's a painful process of tracking down performance issues. For example:
https://twitter.com/cnjunyi/status/1607056174612119553?s=20&t=-Jcq3KLOuB8UU7M_1wPpvQ
logseq/logseq#8137

We should setup a FAQ on the forum https://discuss.logseq.com/c/faq/6 to help saving the communication cost of the process. Then make it to the document.

Some basic text pieces on the topic:
Most performance degradation happens when edited from outside, may caused by cache corruption. Try best to collect the way to reproduce the performance degradation.
To reset the cache issue, may try in following steps: Re-index. Clear cache.
A performance profile will be super helpful https://help.figma.com/hc/en-us/articles/360041468414-Record-a-Chrome-Performance-Profile
Locating the content that cause the performance issue will be very helpful

@cnrpman cnrpman converted this from a draft issue Jan 11, 2023
@cnrpman cnrpman added the documentation Improvements or additions to documentation label Jan 11, 2023
@cnrpman cnrpman moved this to PR welcome! in Logseq - Develop Together 💪 Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Development

No branches or pull requests

1 participant