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

Head-truncate time series files only if a certain percentage of size decrease is accomplished #1296

Closed
beorn7 opened this Issue Jan 8, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@beorn7
Copy link
Member

beorn7 commented Jan 8, 2016

Servers with a very long retention period have series files with a lot of chunks. Even if only a single chunk at the beginning of the file is removed in series maintenance, the whole file is rewritten. This causes a lot of I/O for very little effect. On spinning disk, the problem doesn't show up that much because series maintenance takes long, and therefore larger changes are batched up implicitly. On SSDs, though, series maintenance is so fast and thus performed so frequently that many of those micro truncations can happen.

Some filesystems support "punching holes", which can be used to head-truncate without rewriting the file. However, that might cause more load for the filesystem, and it's not a general solution as not all filesystems support it.

An easy solution is to only rewrite the series file if a certain percentage of the total size is head-truncated. With e.g. 10%, the overhead in wasted disk space is limited but the I/O load will be reduced quite a bit.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.