how to reduce TIME_WAIT

[ZIZAZA]

weblogic 8.1.6 installed on hpux 11.31
there are about 15000 tcp TIME_WAIT when loadrunner test. how can i reduce TIME_WAIT?

[Johnson Punniyalingam]

Check below thread

you can reduce the TCP_TIME_WAIT using ndd command

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1031869

[Matti_Kurkela]

Rick Jones from HP says HP-UX can handle millions of connections in TIME_WAIT state without significant performance impact and using very little memory to do that.

So do you have a real issue because of 15 000 TIME_WAITs, or are you asking just because the long netstat listing "looks bad"?

ftp://ftp.cup.hp.com/dist/networking/briefs/annotated_ndd.txt

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1398855

MK

[rick jones]

Let me guess - loadrunning is starting to be unable to establish more connections? At the risk of repeating what is in the URLs, TIME_WAIT is there for a purpose - to protect new connections with the same "name" from old, delayed segments from previous connections by that name.

Given that the default anonymous port space in HP-UX is ~16K (49152 to 65535) and the statement of "about 15000" I would guess that whatever loadrunner is being asked to do involves connecting to a fixed remote IP and port number from the one local IP address and the anonymous port range.

Rather than shrink TIME_WAIT it would be "best" to do more work per TCP connection.

If that is not possible, then it would be "better" to get the loadrunner code to start making explicit local port number bindings from the "full" range of say 5000 to 65535. If that is not possible, then it would be "good" increase the size of the anonymous port space by tweaking tcp_smallest_anon_port.

Somewhere in all that would also be getting the load runner code to make use of more than one local IP address. Particularly if you are trying to simulate lots of remote clients connecting to the weblogic service provided by the system...

The whole idea is to increase the number of available/utilized "names" for TCP connections by increasing the number of local port numbers and/or IP addresses being used.