Skip to contentSkip to conversation

SOMAXCONN - bump up or sysctl?

DISCUSSION Tim Hockin 3 participants 3 messages Jul 13, 2001

lore
Share & tools
lore

Tim Hockin

author
#0 lore raw

hey all,

We have a request to bump up SOMAXCONN. Are there are repurcussions to doing so? Would it be better to make it a sysctl?

Signature · 4 lines
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
[email protected]
#1 lore raw
Quoted 2 lines · Tim Hockin

We have a request to bump up SOMAXCONN. Are there are repurcussions to doing so? Would it be better to make it a sysctl?

There is a very serious repurcussion to allowing this be increased in any form, people won't fix their code if you just give them this bandaid.

The new connection backlog controlled by an upper limit of SOMAXCONN is a "buffer" between the kernel and userspace.

It is _NOT_ a permanent storage area inside the kernel for new connections. Once people writing these apps start thinking about it as a buffer (ie. think "temporary"), the thought to increase SOMAXCONN will occur less often in their minds.

I have never been shown a legitimate argument for increasing SOMAXCONN.

Later,
David S. Miller
[email protected]

#2 lore raw
In reply to Tim Hockin
Quoted 2 lines

We have a request to bump up SOMAXCONN. Are there are repurcussions to doing so? Would it be better to make it a sysctl?

Its pretty meaningless as a value. People who say they need a larger SOMAXCONN are as a general rule simply wrong in the Linux case