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

perf: flush timeout might trigger aggressive compression #94

Closed
kruskall opened this issue Dec 7, 2023 · 0 comments
Closed

perf: flush timeout might trigger aggressive compression #94

kruskall opened this issue Dec 7, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@kruskall
Copy link
Member

kruskall commented Dec 7, 2023

With compression enabled the docappender will use gzip to compress the bulk requests. The gzip writer buffer data by default for more efficient compression but if we hit a flush timeout the gzip writer is closed and the buffered data is forced into the compression pipeline.

Ideally, we should not compress small requests as it will cause increased cpu usage and poor compression ratio.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants