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.

Sign up for GitHub

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

Jump to bottom

as much as it hurts, async is holding us back #9

Closed
wants to merge 2 commits into from
Closed

as much as it hurts, async is holding us back #9

wants to merge 2 commits into from

Commits on Jun 17, 2023

  1. as much as it hurts, async is holding us back 

    About my testing: for some reason, I can't push loopback further than ~40Gbit/s on my machine, no matter the connections.

On the other hand, if I only flood with a single connection, I get ~10Gbit/s with sturmflut with the async version, with breakwater running at 102% cpu. With the sync version, I get ~14Gbit/s, still at 102% cpu usage.

I'm not saying that I like the sync version more than the async version, but it is definitely noticeably faster. If I hammer them with 10 connections, both versions perform similar in terms of bandwidth.
    @fabi321
    fabi321 committed Jun 17, 2023
    Configuration menu
    Copy the full SHA
    2f2adf8 View commit details
    Browse the repository at this point in the history

Commits on Jun 18, 2023

  1. sync tests

    @fabi321
    fabi321 committed Jun 18, 2023
    Configuration menu
    Copy the full SHA
    8d4204e View commit details
    Browse the repository at this point in the history