network speed on t2000
in [Solaris]
|
From: jdh13 on 8 Feb 2007 07:46 hi all, when transfering data between two t2000, i noticed a bad speed, so i did some tests: t2000_A e1000g0 --- switch HP 2824 --- e1000g0 t2000_B t2000_A e1000g3 ---------------------- e1000g3 t2000_B i'm using netperf, and in all cases, i got around 300 Mbit/s if i run 3 netperf in parallel, each one displays around 100 Mbit/s Has anyone noticed it on this kind of machine? All are Solaris 10 U3 with latest patches thanks in advance, gerard
From: Dan Foster on 8 Feb 2007 07:51 In article <45cb1bb5$0$419$426a74cc(a)news.free.fr>, jdh13 <jdh13(a)free.fr> wrote: > > when transfering data between two t2000, i noticed a bad speed, so i > did some tests: > > i'm using netperf, and in all cases, i got around 300 Mbit/s What is the performance if you enable jumbo frames? (9000 byte MTU on both host side and switch side) -Dan
From: jdh13 on 8 Feb 2007 08:19 Dan Foster wrote: > In article <45cb1bb5$0$419$426a74cc(a)news.free.fr>, jdh13 <jdh13(a)free.fr> wrote: >> when transfering data between two t2000, i noticed a bad speed, so i >> did some tests: >> >> i'm using netperf, and in all cases, i got around 300 Mbit/s > > What is the performance if you enable jumbo frames? > > (9000 byte MTU on both host side and switch side) > but it works well for others machines like Sun V40z (opteron, solaris 10), Sun V65x (linux) and mtu is 1500, i got around 800 Mbit/s and what is it bad is that you have to reboot T2000 to change MTU, because, strangely, MaxFrameSize 0 Standard ethernet frames with a MTU equal to 1500. Default. and: t2000-root% ifconfig e1000g3 mtu 9600 ifconfig: setifmtu: SIOCSLIFMTU: e1000g3: Invalid argument so if i modify e1000g.conf, i have to reboot! why this driver is such configured?
From: Casper H.S. Dik on 8 Feb 2007 10:03 jdh13 <jdh13(a)free.fr> writes: >and: >t2000-root% ifconfig e1000g3 mtu 9600 >ifconfig: setifmtu: SIOCSLIFMTU: e1000g3: Invalid argument >so if i modify e1000g.conf, i have to reboot! >why this driver is such configured? update_drv -f e1000g did not cause the changes to be picked up? (note that 9000 is the maximum jumbo frame size) The driver was written by Intel so I don't know why they did it this way. What TCP window sizes did you use? Casper -- Expressed in this posting are my opinions. They are in no way related to opinions held by my employer, Sun Microsystems. Statements on Sun products included here are not gospel and may be fiction rather than truth.
From: jdh13 on 8 Feb 2007 10:19
Casper H.S. Dik wrote: > jdh13 <jdh13(a)free.fr> writes: > >> and: >> t2000-root% ifconfig e1000g3 mtu 9600 >> ifconfig: setifmtu: SIOCSLIFMTU: e1000g3: Invalid argument >> so if i modify e1000g.conf, i have to reboot! >> why this driver is such configured? > > update_drv -f e1000g did not cause the changes to be picked up? > i didn't known this ability to change a parameter without rebooting > (note that 9000 is the maximum jumbo frame size) > > The driver was written by Intel so I don't know why they did it > this way. What TCP window sizes did you use? > finally, i found these commands: t2000-root% ndd -get /dev/e1000g0 \? .... max_frame_size (read only) .... t2000-root% ndd -get /dev/e1000g0 max_frame_size 1514 |