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
compress/gzip: pooling flate.Writer #65114
Comments
Taking this out of the proposal process as it does not require api changes. I think adding a pool for flate is valid given the improvements in performance. |
Can i contribute this issue? |
How much of the difference would there be between pooling writers and compressors?
This looks like a custom benchmark, could you provide the code please? |
@AlexanderYastrebov I found that depending on compression level, benchmark can be different. so i change benchmark above.
|
I don't think it's wise to add pooling in situations where In this situation, the call to
With the current API, pooling should be the responsibility of the user. |
OK. I understood. Thank you for answering! |
Proposal Details
can pooling
flate.Writer
below?Before:
After:
I know that when using
gzip.Writer
, most case use pool ofgzip.Writer
. but poolingflate.Writer
can reduce memory pressure slightly more.The text was updated successfully, but these errors were encountered: