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

Disable nagles alg #63

Merged
merged 4 commits into from
Jul 16, 2024
Merged

Disable nagles alg #63

merged 4 commits into from
Jul 16, 2024

Conversation

KronosTheLate
Copy link
Contributor

Closes #54.

This PR adds a single line to disable nagles algorithm, using the Sockets.nagle function. This is done on the client side, inside the setup_connection! function.

On my system, the effect is that @btime @remote 1+1 goes from 44.5 ms to 0.601 ms, or a 74x speedup. As the operation itself (1+1) takes 1.4 ns, we can say we are approximately timing the overhead. So in other words, the overhead of calls to @remote is reduced 74-fold.

I have made no changes to any documentation, and I have not performed any more than a single test. I am not sure if we should expect this to break anything, as the change is rather minor. Testing was done on Julia 1.9.3.

@KronosTheLate
Copy link
Contributor Author

Ping @c42f have you found time to take a look at this?

KronosTheLate and others added 3 commits July 16, 2024 02:03
Add a bunch of potential error messages in "troubleshooting.md"
This ensures it's in a standard section of the docs and will be built
with the rest of the docs.
@c42f c42f merged commit 24a5901 into JuliaWeb:main Jul 16, 2024
4 checks passed
@c42f c42f mentioned this pull request Jul 16, 2024
@KronosTheLate
Copy link
Contributor Author

Thanks for getting around to it. I know you are busy with other important stuff. I am pretty sure I was watching you live on the Juliacon stage when I wrote the previous comment xD

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

Successfully merging this pull request may close these issues.

Significant overhead/latency (about 50ms)
2 participants