We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems to me that bbolt starts 'write' of pages to disk when the transaction is committed:
bbolt/tx.go
Line 537 in 90fdc8d
Taking in consideration that:
I think bbolt for etcd should:
leaf
It should make the disk usage way more 'uniform' and commit locks substantially shorter.
Extracted from: etcd-io/etcd#12924
The text was updated successfully, but these errors were encountered:
cenkalti
No branches or pull requests
Write pages ASAP (optimistically)
It seems to me that bbolt starts 'write' of pages to disk when the transaction is committed:
bbolt/tx.go
Line 537 in 90fdc8d
Taking in consideration that:
I think bbolt for etcd should:
leaf
pages to disk as soon as they are full (even before commit was called).It should make the disk usage way more 'uniform' and commit locks substantially shorter.
Extracted from: etcd-io/etcd#12924
The text was updated successfully, but these errors were encountered: