Description:
I am encountering significant performance issues when using Logseq with longer pages, particularly those around or above 1,600 lines in org syntax. The presence of embedded code blocks seems to exacerbate the issue.
Details:
Page Length: Approximately 1,600 lines, written in org syntax.
Content: Notes with embedded code samples
Issue: As the length and complexity of the page have increased, I’ve found it increasingly difficult to edit or update due to severe lag.
Resource Consumption:
Memory: Logseq uses up to 1.7 GB of RAM when this page is opened.
CPU Usage: I’ve observed around 30% CPU usage when simply scrolling up and down the page.
Thanks, I understand it may not be an easy fix. But long-form page with code snippets is essential to my workflow. Would be great to fix it later on. For now, I will keep an eye on page length and split when it grows too long.
There is nothing wrong with embed page/block
But The style can be inconsistent
Block Array is supposed to look like block Object. But it is a bit distracting.
I agree this is a workaround for me ATM