> [tdavis@pdsflx16 bonnie]$ ./bonnie -d /data01/b -s 1024
> File '/data01/b/Bonnie.2268', size: 1073741824
> Writing with putc()...done
> Rewriting...done
> Writing intelligently...done
> Reading with getc()...done
> Reading intelligently...done
> Seeker 3...Seeker 2...Seeker 1...start 'em...done...done...done...
> -------Sequential Output-------- ---Sequential Input--
> --Random--
> -Per Char- --Block--- -Rewrite-- -Per Char- --Block---
> --Seeks---
> Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU
> /sec %CPU
> 1024 5298 81.1 7138 17.2 4270 17.8 4826 70.1 9980 13.3
> 389.1 6.2
>
> mount options:
> starsu00.nersc.gov:/data01 on /auto/data01 type nfs
> (rw,hard,intr,rsize=8192,wsize=8192,addr=128.55.129.74)
>
> starsu00 is e450, 4x248mhz cpus, 1GB ram, ~400GB of disk
> (18x18GB+4x23GB) solaris 2.6
Doesn't the solaris server normally select a 32k rsize/wsize if you
don't force it to 8k? If it does, that should give better performance.
With NFSv3, you generally don't want to force the rsize/wsize unless
your machine has limited memory or the network bandwidth is low. The
client itself will select the optimal value based on the server
preferences.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/