Reported by g_makulik (1256748435|%O ago)
Without having tested the hint about using the -tcp_nodelay option, a question comes to my mind:
Is it implemented by just setting TCP_NODELAY for the involved socket, or is there
a decision made dynamically to flush the buffers or not, depending on the amount
of messages queued for sending?
I'm afraid that just using the socket attribute could worsen the behavior dramatically
if there are lots of messages to send.
No files attached to this page.
Edit | Files | Tags | Print
Who's following this issue?
Submitted by g_makulik
Use one of these tags to say what kind of issue it is:
- issue - a fault in the software or the packaging or the documentation.
- change - a change or feature request.
Use one of these tags to say what state the issue is in:
- open - a new, open issue.
- closed - issue has been closed.
- rejected - the issue has been rejected.
Use one of these tags to say how urgent the issue is:
- fatal - the issue is stopping all work.
- urgent - it's urgent.