-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
I just have to create a new issue since its still problematic for me..
Description:
Upon utilizing FreshRSS with MariaDB (version 10.6) under the Docker edge tag, there’s still an evident high resource usage and subsequent 504 timeouts during specific operations. The FreshRSS database CPU utilization spikes to approximately only 20% (should use more in my opinion since this states its not really optimized) and high IO disk usage, which reaches around 1GB/s, have been observed to last for a few minutes during several actions.
Problematic Actions:
- Actualize Script Execution: Triggering the script manifests in a substantial resource strain for ~ 4 minutes.
- Adding New Feeds: While the feed does get added, the operation culminates in a 504.
- Viewing Idle Feeds: Invariably results in a 504 and is never accessible.
- General Feed Statistics: Unreachable due to a perpetual 504.
Insights and Potentials:
Although the functions eventually serve their intended purpose (aside from viewing idle feeds and statistics), the undue strain and resulting timeouts mar the usability and efficiency of the system. A deductive observation points towards the possibility that the database queries still might not be wholly optimized for use with MariaDB, potentially requiring a revisit and refinement to enhance performance, especially in the aforementioned contexts.
I hope I can be of any help.by providing logs or testing development builds.
Previous Discussion:
It’s notable that the 504 issue has been broached before, its been solved for "Marking all News as Read" which is now done in a matter of seconds, yet it still pervasively persists through these other actions. Alleviating this would drastically improve the overall user experience and system reliability.
Potential Resolution:
Optimizing how MariaDB processes queries, especially during intensive operations such as those highlighted, might hold the key to alleviating the resource burdens and the subsequent 504 timeouts.
Any insights, assistance, or pointers on this would be massively appreciated!
Kind Regards.