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.

Sign up for GitHub

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

Jump to bottom

Modify disk buffer size calculations to evaluate deleted objects size correctly and estimate the speed of the deletion #7275

Closed
abuts opened this issue Jan 25, 2013 · 1 comment
Closed

Modify disk buffer size calculations to evaluate deleted objects size correctly and estimate the speed of the deletion #7275

abuts opened this issue Jan 25, 2013 · 1 comment
Assignees
@abuts
Labels
Vates
Milestone
Release 2.5

Comments

@abuts
Copy link
Member

abuts commented Jan 25, 2013

Current DiskBuffer implementation not uses the size of the object which was inserted in the buffer to estimate the free space changes when the object was deleted.

The size of the new object is used instead.

In addition to that (it looks like) the object deletion uses search in the cache to remove object from the cache. Despite search is logarithmic vrt the buffer, constant search would be more appropriate for this situation.

These things request investigation and improvement.
@abuts abuts added the Vates label Jun 3, 2015
@abuts abuts self-assigned this Jun 3, 2015
@abuts abuts added this to the Release 2.5 milestone Jun 3, 2015
@abuts abuts closed this as completed Jun 3, 2015
@abuts
Copy link
Member Author

abuts commented Jun 3, 2015

This issue was originally trac ticket 6429

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abuts abuts

Labels
Vates
Projects
None yet
Milestone
Release 2.5
Development

No branches or pull requests
1 participant
@abuts