-
-
Notifications
You must be signed in to change notification settings - Fork 439
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
Loading main page makes server CPU max out #902
Comments
Can you go to the admin panel and share how big is the size of your assets? Also, btw, Hoarder now has official support for single file (#172 (comment)) though it's still in the nightly release. |
When I look inside the docker volumes, the folder assets contains just 126MB. BTW the bug also seems to be triggered by opening the 'Broken links' page, if that's any help. I read about the direct singlefile integration, but I'm using a companion API I wrote myself to send articles to 2 services (Zipline and Hoarder), for the purpose of being able to share the link to others as well. |
The fact that it gets trigged in the broken links page is very interesting because this page is very lightweight in general (it doesn't even touch the content of the URLs themselves). It's basically just a single database query. And given that you have only 16 bookmarks, it should be extremely fast. How big is the |
The |
I tried the broken links page again, and this time it didnt happen, so that was perhaps not a trigger. Sorry about that. Going back to the main bookmarks page again for the third time triggered 100% CPU again though.. |
17MB for 16 bookmarks is a lot, but it's not crazy high. Is your database file local or on NFS/Samba? |
It's local storage. |
hmmm, it's going to be hard to debug this without a repro unfortunately. |
Is there not a way for me to deliver more logs, like a debug mode or something? |
Describe the Bug
Hi!
As I described earlier in this issue, I seem to have a quite annoying bug that makes my VM I run Hoarder on go to 100% CPU usage and makes my VM unusable for like 10-20 minutes.
My hoarder data consists of 16 imported articles, however these URLs point to hosted versions of Singlefile HTML archives.
It could perhaps be that these articles contain a lot of data since they are full page archives and this somehow causes this bug.
I can reproduce this bug by simply opening the page again, so it's not a one-off issue.
Steps to Reproduce
Expected Behaviour
Open hoarder main page and see my 16 articles there, without any performance issues.
Screenshots or Additional Context
This is the log from around the time I loaded the page:
Device Details
No response
Exact Hoarder Version
0.21.0
Have you checked the troubleshooting guide?
The text was updated successfully, but these errors were encountered: