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
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.
The text was updated successfully, but these errors were encountered:
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?
If you go so far as to benchmark compression of HTTP bodies to/from the network with some amount of concurrency (a full stack kind of simulation), then you might want to try something like this to see if size of Stream<Item> buffers (as it relates to time blocking reactor threads) matters:
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.
The text was updated successfully, but these errors were encountered: