Skip to content
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

[leo_storage] Avoid write operations at more earlier timing than #592 do #1179

Open
mocchira opened this issue Dec 26, 2018 · 0 comments
Open

Comments

@mocchira
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants