- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- parameter tuning tcp_conn_request_max
Operating System - HP-UX
1748136
Members
3560
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2010 11:32 PM
тАО08-29-2010 11:32 PM
parameter tuning tcp_conn_request_max
Hi,
I need to tune the parameter tcp_conn_request_max=8192.
I have checked nddconf file above line is not availble and how to make it.
regards
panneer
I need to tune the parameter tcp_conn_request_max=8192.
I have checked nddconf file above line is not availble and how to make it.
regards
panneer
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2010 11:43 PM
тАО08-29-2010 11:43 PM
Re: parameter tuning tcp_conn_request_max
Hi ,
There are already so many threads on this.
You can put an entry if it is not there.
If you want to set temporary, you can use
ndd -set command
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=943817
From Rick's document
ftp://ftp.cup.hp.com/dist/networking/briefs/annotated_ndd.txt
tcp_conn_request_max:
Maximum number of outstanding inbound connection requests.
[1, - ] Default: 20 connections
This is also known as the maximum depth of the "listen queue." The
actual maximum for any given TCP endpoint in the LISTEN state will be
the MINIMUM of tcp_conn_request_max and the value the application
passed-in to the listen() socket call.
For this parameter to take effect for a given application, it must be
set BEFORE said application makes its call to listen(). So, if you use
ndd to set this value after the application has started, it will have
no effect unless you can get the application to recreate its LISTEN
endpoint(s).
You can see if tcp_conn_request_max MIGHT be too small by looking at
the output of either "netstat -s" or "netstat -p tcp" and looking for
the line displaying the number of connection requests dropped due to
full queue. If the number of drops is zero, the value of
tcp_conn_request_max is fine. If the value is non-zero, either
tcp_conn_request_max is too small, or the values the applications are
using in their calls to listen() are too small.
Setting this value higher has no particular downside. Editing
/etc/rc.config.d/nddconf to set this value to say 1024 is probably not
a bad idea for any "internet server" system.
Regards,
Sooraj
There are already so many threads on this.
You can put an entry if it is not there.
If you want to set temporary, you can use
ndd -set command
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=943817
From Rick's document
ftp://ftp.cup.hp.com/dist/networking/briefs/annotated_ndd.txt
tcp_conn_request_max:
Maximum number of outstanding inbound connection requests.
[1, - ] Default: 20 connections
This is also known as the maximum depth of the "listen queue." The
actual maximum for any given TCP endpoint in the LISTEN state will be
the MINIMUM of tcp_conn_request_max and the value the application
passed-in to the listen() socket call.
For this parameter to take effect for a given application, it must be
set BEFORE said application makes its call to listen(). So, if you use
ndd to set this value after the application has started, it will have
no effect unless you can get the application to recreate its LISTEN
endpoint(s).
You can see if tcp_conn_request_max MIGHT be too small by looking at
the output of either "netstat -s" or "netstat -p tcp" and looking for
the line displaying the number of connection requests dropped due to
full queue. If the number of drops is zero, the value of
tcp_conn_request_max is fine. If the value is non-zero, either
tcp_conn_request_max is too small, or the values the applications are
using in their calls to listen() are too small.
Setting this value higher has no particular downside. Editing
/etc/rc.config.d/nddconf to set this value to say 1024 is probably not
a bad idea for any "internet server" system.
Regards,
Sooraj
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2010 05:10 AM
тАО08-31-2010 05:10 AM
Re: parameter tuning tcp_conn_request_max
in fact you can add any ndd configuration to nddconf.
just add
TRANSPORT_NAME[0]=tcp
NDD_NAME[0]=tcp_conn_request_max
NDD_VALUE[0]=8192
in fact the 0 is the index of the table so if you already have configurations in your ndd conf, you must use index+1 for your cnfiguration
just add
TRANSPORT_NAME[0]=tcp
NDD_NAME[0]=tcp_conn_request_max
NDD_VALUE[0]=8192
in fact the 0 is the index of the table so if you already have configurations in your ndd conf, you must use index+1 for your cnfiguration
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP