Solaris

Following command was set up in startup script on Solaris 8 servers - improved network transfers of files from one server to the another [server B has duplicate entry in it's startup script except the IP is changed to server A] (doubled transfer speed).

Code:

ndd -set /dev/tcp tcp_host_param '10.140.20.10 sendspace 279600 recvspace 279600 timestamp 1'

Now they are getting a new server with Solaris 10 on it - setting the same command in a startup script does NOTHING for the speed of the transfer.

both networks are 100 MB - new server on same subnet as old one. New server will get old server's IP (so nothing on the server B side has to change)

Anyone know what might be the 'new' way of doing this for Solaris 10?

What are the model of the Solaris 8 and 10 machines?
Are they sparc or x86 ?

What performance are you measuring with the Solaris 8 and 10 servers ?

This ndd setting is doomed anyway:
Bug ID: 6737341 tcp_host_param should be removed

Both are sparc machines and the application is using scp (F-secure I think) to measure 'speed'. The server A has a qfe card - the tcp_host_param is set on only one of the interfaces and it has 1.3MBs versus 512MBs to the interface with the default tcp_host_param setting.

Again, the question is what parameter (if any) would need to be set to get the same type of boost (obviously the tcp_host_param doesn't do it anymore - actually, the transfer does use the tcp_host_param setting when the scp happens [can be seen with netstat -an send-q/recv-q] but it doesn't cause it to go any faster, as it did between 2 Solaris 8 servers).

I'm no asking what performance you measure with Solaris 8 with and without the tuning but the performance measured with Solaris 10 vs Solaris 8.

Application is using the output from the scp -

examples are all from old Solaris 8 server:

to 1st interface on old solaris 8 server with tcp_host_param settings set higher

Code:

snoop5.out                            |  866MB | 1.1MB/s |TOC: 00:13:14 | 100%

to 2nd interface on old solaris 8 server with no special tcp_host_param set up

Code:

snoop5.out                            |  866MB | 756kB/s |TOC: 00:19:32 | 100%

to new server (solaris 10) with tcp_host_param settings set higher

Code:

snoop5.out                            |  866MB | 413kB/s |TOC: 00:35:48 | 100%

So, they are looking to get the solaris 10 to have the same "speed" as they see on the old solaris 8 server.

maybe because of the global cap on window wize, try this:

Code:

ndd -set /dev/tcp tcp_xmit_hiwat 279600
ndd -set /dev/tcp tcp_recv_hiwat 279600

TCP Tunable Parameters (Solaris Tunable Parameters Reference Manual) - Sun Microsystems