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
As reported on #1156 (comment), #592 worked as we intended and succeeded in avoiding that the disk full happens however it turned out that the compaction on LeoStorage which available disk space is really small took so much time as the less available disk space there is, the more time any disk operations (seek/read/write) tend to take (because there are barely physically continuous disk blocks).
That being said, we may have to avoid write operations more earlier timing at which the compaction throughput isn't degraded.
NEED BENCHMARK.
The text was updated successfully, but these errors were encountered:
This issue is a follow up for #592.
As reported on #1156 (comment), #592 worked as we intended and succeeded in avoiding that the disk full happens however it turned out that the compaction on LeoStorage which available disk space is really small took so much time as the less available disk space there is, the more time any disk operations (seek/read/write) tend to take (because there are barely physically continuous disk blocks).
That being said, we may have to avoid write operations more earlier timing at which the compaction throughput isn't degraded.
NEED BENCHMARK.
The text was updated successfully, but these errors were encountered: