You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the git commit history, I found that the sync pool of the gzip writer was removed. The reason is to fix the issue here: labstack/armor#13. But I still don't understand the reason for this deletion. I guess tha Is it because there is no way to return an error when using sync pool?
Adding a sync.Pool for the *gzip.Writer reduces the allocations of the
Compress middleware in 50% and gives an increase on execution speed of
a 85%
This fixlabstack#1643
I did the change and I could see some improvements on the speed and the number of allocations. Please take a look at the PR and check that the implementation makes sense.
Looking at the git commit history, I found that the sync pool of the gzip writer was removed. The reason is to fix the issue here: labstack/armor#13. But I still don't understand the reason for this deletion. I guess tha Is it because there is no way to return an error when using sync pool?
the removed code:
The text was updated successfully, but these errors were encountered: