You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that tribler makes very high amounts of write requests to the disk, sometimes around 400-600KB/s constantly even when all Downloads are stopped this is going on.
Upon further investigation with Procmon i found that Tribler is doing thousands of WriteFile Requests per second inside.
C:\Users\clusterfuck\AppData\Roaming.Tribler\8.0\sqlite
According to Perfmon around 24.000+ write req/s average:
This may wear out some SSDs on the long term, cause higher CPU usage and maybe it is even slowing down the tribler process itself.
So perhaps it would be usefull if someone has a closer look on what is going on there.
The text was updated successfully, but these errors were encountered:
nitmeare
changed the title
relatively high amount of write requests in 8.0.4
High amount of Disk write requests in 8.0.4
Nov 24, 2024
Our database (ORM library) should take care of batching writes to your disk to avoid exactly this issue. Perhaps we misconfigured it? We'll check it out.
@egbertbouman mitigated the disk writes in #8274 However, my earlier claim..
Our database (ORM library) should take care of batching writes to your disk to avoid exactly this issue.
..shockingly, did not turn out to be true. We will need to make some bigger changes in our own code base to properly solve this issue. Because this issue requires a big refactoring effort, we'll schedule this for the next stable release, 8.1.0.
I found that tribler makes very high amounts of write requests to the disk, sometimes around 400-600KB/s constantly even when all Downloads are stopped this is going on.
Upon further investigation with Procmon i found that Tribler is doing thousands of WriteFile Requests per second inside.
C:\Users\clusterfuck\AppData\Roaming.Tribler\8.0\sqlite
According to Perfmon around 24.000+ write req/s average:
This may wear out some SSDs on the long term, cause higher CPU usage and maybe it is even slowing down the tribler process itself.
So perhaps it would be usefull if someone has a closer look on what is going on there.
The text was updated successfully, but these errors were encountered: