Joseph Bishop wrote:
Dan,
Do a sanity check with sysstat 1.
See if the CPU is at or near 100% when moving the data. You may have CPU or disk limitation before breaking the 100Mbit barrier.
My best performance thus far is with client using NFS3, TCP, RSIZE=16384.
mlswna:/ on /backup/mnt/mlswna/rt type nfs (ro,timeo=14,rsize=16384,wsize=16384,nfsvers=3,tcp,addr=209.41.211.225)
-rw-r--r-- 1 34726 34726 524288000 Jul 11 09:15 /backup/mnt/mlswna/rt/home/dobrien1/diskfile500
55.58s real 0.04s user 1.51s system
That's only 9,433,033.46 Bytes/Second.
This is the tail end of sysstat 1 on the filer:
54% 710 0 0 432 12282 11424 0 0 0 1 47% 624 0 0 382 10796 9936 0 0 0 1 47% 647 0 0 396 11206 10350 0 0 0 1 52% 670 0 0 408 11600 10710 0 0 0 1 49% 601 0 0 371 10399 9657 0 0 0 1 49% 596 0 0 366 10315 9504 0 0 0 1 54% 602 0 0 371 10429 10054 460 0 0 1 49% 584 0 0 361 10118 9341 0 0 0 1 39% 458 0 0 282 7927 7324 0 0 0 1 48% 579 0 0 359 10032 9293 0 0 0 1 48% 572 0 0 352 9910 9157 0 0 0 1 33% 417 0 0 259 7225 6698 0 0 0 1 56% 660 0 0 406 11422 10544 0 0 0 0 49% 595 0 0 366 10308 9585 0 0 0 0 39% 488 0 0 301 8455 7803 0 0 0 0 39% 476 0 0 292 8238 7584 0 0 0 0 38% 461 0 0 284 7987 7351 0 0 0 0 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 41% 458 0 0 284 7934 7571 348 0 0 0 42% 516 0 0 320 8940 8280 0 0 0 0 42% 528 0 0 320 9001 8284 0 0 0 0 40% 500 0 0 310 8662 8068 0 0 0 0 47% 565 0 0 348 9788 9001 0 0 0 0 48% 584 0 0 362 10117 9385 0 0 0 0 62% 728 0 0 448 12599 11644 0 0 0 0 40% 483 0 0 298 8368 7727 0 0 0 0 50% 604 0 0 372 10464 9653 0 0 0 0 50% 603 0 0 370 10420 9620 0 0 0 0 45% 534 0 0 331 9251 8564 0 0 0 0 48% 539 0 0 334 9338 8904 364 0 0 0 31% 389 0 0 240 6736 6150 0 0 0 0 1% 0 0 0 0 0 0 0 0 0
I'm pushing the filer around 50% busy.
I've not tweaked MTU yet.
What happens when I set the MTU higher and the filer talks to other system with MTU of only 1500 bytes? Is it negotiated?
Regards,
Dan O'Brien, dmobrien@lcsi.net Cell: 614-783-4859 Work: 614-476-8473 Home: 740-927-2178 Pataskala, OH