Score:0

Optimize small Websocket messages with nginx "tcp_nopush off"?

de flag

I'm currently using nginx as a reverse proxy for a websocket server that very frequently broadcasts tiny messages; often 1 - 2 bytes in length. I'm trying to minimize latency as much as possible.

It's commonly recommended that tcp_nopush on; be set in nginx.conf so that packets are only sent once they reach the MSS. Given my primary use case is sending very small websocket messages, would it make sense to disable this for the websocket location block, while still keeping tcp_nodelay on; ? Would the potential trade-off between potentially increased congestion and more immediate sending still work out in favor of disabling it?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.