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

Benchmarks! #50

Open
Nemo157 opened this issue Oct 15, 2019 · 1 comment
Open

Benchmarks! #50

Nemo157 opened this issue Oct 15, 2019 · 1 comment

Comments

@Nemo157
Copy link
Owner

@Nemo157 Nemo157 commented Oct 15, 2019

Should be pretty easy to throw together some benchmarks comparing the different async variants against their synchronous counterparts to see how much overhead the async state machines introduce.

@dekellum

This comment has been minimized.

Copy link

@dekellum dekellum commented Jan 13, 2020

Hi, have you considered the implications of doing compress/decompress on the reactor thread vs. some other coordination strategy or dispatching to non-reactor thread?

Good benchmarks should be able to inform any "default" strategy atleast?

See: http://gravitext.com/2020/01/13/blocking-permit.html

Does the newer async-compression worry about blocking a reactor thread? Should it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.