-
Notifications
You must be signed in to change notification settings - Fork 70
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
enable gzip and deflate in http client #328
Conversation
I ran current -dev w/o this patch, and current -dev w/ this patch, each 3 times as follows (restarting all server processes before each batch of 3):
Here's the data: Goose made >30% more anonymous requests, but 5.6% fewer authenticated requests with this patch applied. Without compression it averaged 6,473 requests per second. With compression it averaged 9,542 requests per second. It would be good to re-run the test with fewer GooseUsers and an evenly balanced number of Anonymous and Authenticated users: my assumption is that the reduction in authenticated traffic is simply because anonymous traffic was being returned so quickly by Varnish that it was getting scheduled far more. The Apache/Varnish server saw no change in CPU usage (as Varnish caches compressed pages), whereas the Goose server saw an increase in CPU usage, visible here (Goose is running in a 32-core VM): Though it made considerably more requests, obviously there was considerably less network traffic generated: |
Let’s also add the request headers to the debug log and:or add a typical HTTP header to the docs. |
Authenticated requests slow down as Apache is compressing each request due to how my server is configured. There's additional CPU usage showing up on the Apache server because of this. |
gzip
support in the http client--no-gzip
orGooseDefault::NoGzip
deflate
and/orbrotli
compression