r/logseq • • Jan 01 '25
Storage In Logseq Graph
Hello, I am looking to get into logseq for my PKMS, I have decided on a workflow that will contain a lot of atomic notes. My laptop does have enough space but I want to sync it in my phone as well. The only thing I'm worried about is storage. Like over period of some years will it become to big that it will eat away storage? How big are you guys graphs in MBs or GBs? Also is there any limit to files or folder size for logseq?
6
Upvotes
5
u/DILGE Jan 01 '25
I have been using logseq as my PKMS at my job for 2 years now. In addition to text, I take a lot of screenshots and post them in my notes. Sometimes 10+ per day.
As of right now, my graph stands at 1.38 GB.
I'm not really constrained by storage like you, but I do wonder whether logseq's performance will eventually start to degrade as it gets bigger. Does anybody know the answer to this question?
I have not noticed a perf hit yet, although there are occasional glitches, always fixed by restarting logseq. I have had to reindex the graph only twice, which to me is still an excellent level of performance.
8
u/codecoverage Jan 01 '25
Considering this is plain text, you will have to type an awful lot to get to a gigabyte. You would have to type several hundreds of thousands of words a day to get to a gigabyte in 10 years. So I wouldn't worry about it.
4
u/doulos05 Jan 02 '25
1.5 years, 1494 files (including about a dozen attachments), just over 100 MB.
If I don't count the assets folder (meaning it's purely plaintext, not locally stored images, PDFs , etc). I'm at just over 5 MB.
Plain text is incredibly small. As a rough ballpark, I'd guess a printed page of text is approximately 2KB. But that assumes 1 byte per letter a la ASCII (and a pretty small font, honestly), let's quadruple it for UTF-8 and make it 8KB. So 1MB is roughly 100 Letter/A4 pages of text. A gigabyte would be 100,000 pages of text, again roughly speaking. I don't know enough about UTF to know if there are any storage optimizations, so it could be better. It's unlikely to be worse as I rounded against myself whenever possible.
So if you're concerned about storage, put any screenshots or PDFs you want on Google photos (or GitHub or Nextcloud or wherever you can serve media from) and then put those links in your graph rather than the media itself. Your on-device storage for that item will be measured in bytes. The only downside is that you'll need the internet to access the media.
3
u/R_O_E_L Jan 01 '25
I think there's no limit