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

should compression be measured? #168

Open
domino14 opened this issue Apr 24, 2024 · 1 comment
Open

should compression be measured? #168

domino14 opened this issue Apr 24, 2024 · 1 comment

Comments

@domino14
Copy link

The following is a trace of an API request. Note the "uncovered" time at the end. If I turn compression off, this uncovered time shrinks by a quite a bit (around 2 ms total)
image

I'd love to see exactly what's taking this response that much longer. It seems like ~10K of data should compress in faster than 2 ms, but I'm actually not sure how long that takes.

@emcfarlane
Copy link
Collaborator

Hi @domino14 thanks for the issue. Currently the mechanisms used by the interceptor don't provide compression. Some exploration work has been done, see this issue.

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

No branches or pull requests

2 participants