Toasters
Configuration : Sun E6000 server running Solaris 8 latest patch level Filer : F880 Cisco Switch 6509(Flowcontrol turned on)
We have recently bought 2- F880 filers and we are in the implementation phases. The weird performance results we are getting with following system settings and mount parameters. The output from "sysstat 1" on filer, shows writes 35 MBPS but reads just very slow or not even generate any traffic. Here are the settings
ndd -set /dev/udp udp_recv_hiwat 65535 ndd -set /dev/udp udp_xmit_hiwat 65535 ndd -set /dev/tcp tcp_recv_hiwat 65535 ndd -set /dev/tcp tcp_xmit_hiwat 65535 ndd -set /dev/ge instance 1 ndd -set /dev/ge adv_pauseTX 1 ndd -set /dev/ge adv_pauseRX 1 ndd -set /dev/ge adv_1000autoneg_cap 0 ndd -set /dev/ge adv_1000fdx_cap 1
set sq_max_size = 30 set nstrpush = 90 set ncsize 8000 set nfs:nfs3_max_threads = 24 set nfs:nfs3_nra =10 set nfs:nfs_max_threads = 24 set nfs:nfs_nra = 10
Mount file system :
mount -o rw,bg,hard,intr,proto=udp,vers=3,rsize=32768,wsize=32768 filer01:/vol/test /test
Test method
dd if=/dev/zero of=/test/foo bs=32k count=50000
I have tried to search some documents on now site for the optimal performance but I could not find any optimal numbers which I should try to achieve. Why reads are chocking up ? anyone has any proven configuration which works optimally ?
Thanks in advance for your inputs and thoughts.
Regards
-Deepak Soneji Flextronics International
UDP and 32K transfers don't mix. Reduce to 8K transfers (nfs.udp.xfersize 8192) or change to TCP, the preferred method in which to use NFS.
/Brian/
Toasters
Configuration : Sun E6000 server running Solaris 8 latest patch level Filer : F880 Cisco Switch 6509(Flowcontrol turned on)
We have recently bought 2- F880 filers and we are in the implementation phases. The weird performance results we are getting with following system settings and mount parameters. The output from "sysstat 1" on filer, shows writes 35 MBPS but reads just very slow or not even generate any traffic. Here are the settings
ndd -set /dev/udp udp_recv_hiwat 65535 ndd -set /dev/udp udp_xmit_hiwat 65535 ndd -set /dev/tcp tcp_recv_hiwat 65535 ndd -set /dev/tcp tcp_xmit_hiwat 65535 ndd -set /dev/ge instance 1 ndd -set /dev/ge adv_pauseTX 1 ndd -set /dev/ge adv_pauseRX 1 ndd -set /dev/ge adv_1000autoneg_cap 0 ndd -set /dev/ge adv_1000fdx_cap 1
set sq_max_size = 30 set nstrpush = 90 set ncsize 8000 set nfs:nfs3_max_threads = 24 set nfs:nfs3_nra =10 set nfs:nfs_max_threads = 24 set nfs:nfs_nra = 10
Mount file system :
mount -o rw,bg,hard,intr,proto=udp,vers=3,rsize=32768,wsize=32768 filer01:/vol/test /test
Test method
dd if=/dev/zero of=/test/foo bs=32k count=50000
I have tried to search some documents on now site for the optimal performance but I could not find any optimal numbers which I should try to achieve. Why reads are chocking up ? anyone has any proven configuration which works optimally ?
Thanks in advance for your inputs and thoughts.
Regards
-Deepak Soneji Flextronics International
Brian/Tim
Great ! READS are greatly improved upto 12-15 mbps after changing xfersize to 8k. Any idea about what magic numbers for read/write I should try to achieve while tuning ?
Another question, why TCP ?
Thanks -Deepak ----- Original Message ----- From: "Brian Long" brilong@cisco.com To: "Deepak Soneji" sonejideepak@hotmail.com Cc: toasters@mathworks.com Sent: Thursday, September 19, 2002 6:47 PM Subject: Re: Sun Solaris 8 optimal performance with F880
UDP and 32K transfers don't mix. Reduce to 8K transfers (nfs.udp.xfersize 8192) or change to TCP, the preferred method in which to use NFS.
/Brian/
Toasters
Configuration : Sun E6000 server running Solaris 8 latest patch level Filer : F880 Cisco Switch 6509(Flowcontrol turned on)
We have recently bought 2- F880 filers and we are in the implementation
phases. The weird
performance results we are getting with following system settings and
mount parameters.
The output from "sysstat 1" on filer, shows writes 35 MBPS but reads
just very slow
or not even generate any traffic. Here are the settings
ndd -set /dev/udp udp_recv_hiwat 65535 ndd -set /dev/udp udp_xmit_hiwat 65535 ndd -set /dev/tcp tcp_recv_hiwat 65535 ndd -set /dev/tcp tcp_xmit_hiwat 65535 ndd -set /dev/ge instance 1 ndd -set /dev/ge adv_pauseTX 1 ndd -set /dev/ge adv_pauseRX 1 ndd -set /dev/ge adv_1000autoneg_cap 0 ndd -set /dev/ge adv_1000fdx_cap 1
set sq_max_size = 30 set nstrpush = 90 set ncsize 8000 set nfs:nfs3_max_threads = 24 set nfs:nfs3_nra =10 set nfs:nfs_max_threads = 24 set nfs:nfs_nra = 10
Mount file system :
mount -o rw,bg,hard,intr,proto=udp,vers=3,rsize=32768,wsize=32768
filer01:/vol/test /test
Test method
dd if=/dev/zero of=/test/foo bs=32k count=50000
I have tried to search some documents on now site for the optimal
performance but I could not
find any optimal numbers which I should try to achieve. Why reads are chocking up ? anyone has any proven configuration which works optimally ?
Thanks in advance for your inputs and thoughts.
Regards
-Deepak Soneji Flextronics International
-- Brian Long | | | Americas IT Hosting Sys Admin | .|||. .|||. Phone: (919) 392-7363 | ..:|||||||:...:|||||||:.. Pager: (888) 651-2015 | C i s c o S y s t e m s
On Thursday, September 19, 2002 11:04:35 PM -0700 Deepak Soneji sonejideepak@hotmail.com wrote: +------ | Brian/Tim | | Great ! READS are greatly improved upto 12-15 mbps after changing xfersize | to 8k. | Any idea about what magic numbers for read/write I should try to achieve | while tuning ? | | Another question, why TCP ? +-----X8
UDP has no retry mechanism so if you loose any of the 22 packets involved in a 32k transfer then you need to start again. A powerful server sending to a weaker client is a good way to ensure that packets are lost. TCP has mechanism to ensure that packets are not lost and hence works better when the packet recipient is the weaker partner.
/Michael -- This space intentionally left non-blank.
-
Brian Long -
Deepak Soneji -
Michael Salmon