linkding-on-fly icon indicating copy to clipboard operation
linkding-on-fly copied to clipboard

Experience running on fly.io with 256MB

Open twnaing opened this issue 6 months ago • 3 comments

With 256MB RAM, there are frequent Out Of Memory (OOM) crashes. The idle RAM is about 220 MB.

Without further configuration, import via html file is okay as long as 300 bookmarks per file. More than that and it crashed with OOM.

For the mass import, I run the linkding in local docker and do the import. Then backup sqlite file (according to the documentation) and replace the sqlite file on fly.io. I have to restart the fly.io. The existing user and user from local import both works.

I followed the fly.io documentation to enable swap and it reduced idle RAM to 180MB.

twnaing avatar Dec 15 '23 07:12 twnaing

hey @twnaing, thank you for the report. Do you think it would be reasonable to recommend 512MB as a base line or do you think the swap solution is enough?

fspoettel avatar Dec 15 '23 07:12 fspoettel

Even with swap solution, I still have OOM crashes. Except OOM mail from fly.io there are no loss of functions.

I have 2 users but only 1 is active. The active user has hundreds of tags and almost 4000 bookarmks. I am using linkding and linkding injector extension on desktop firefox, and sharing shortcuts from android and iOS. When using via browser, quick successive navigation resulted in white blank page. However it worked when try again later.

fly.io mail mentions that if I do not want to see the OOM I can unsubscribe.

In summary, 256 MB is workable with minor inconvenience.

twnaing avatar Dec 17 '23 10:12 twnaing

one thing that significantly elevates memory usage is turning on the Pre-load page information while browsing setting in the extension. turning that off resolved oom crashes for me in the past.

fspoettel avatar Dec 19 '23 12:12 fspoettel