logseq / docs

Logseq documentation
https://docs.logseq.com
MIT License
124 stars 90 forks source link

Document for "How to track performance issues" #59

Open cnrpman opened 1 year ago

cnrpman commented 1 year ago

It's a painful process of tracking down performance issues. For example: https://twitter.com/cnjunyi/status/1607056174612119553?s=20&t=-Jcq3KLOuB8UU7M_1wPpvQ https://github.com/logseq/logseq/issues/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