Ben Rockwood wrote: > > I was doing some NFS benchmarking over the weekend with undesirable > results. I thought that I'd use a share from tmpfs in order to contrast > my results. I expected line speed NFS performance... but the results > were horrible, far slower than any disk-based NFS benchmark. > > Is there some reason why tmpfs NFS shares would preform horribly? Or, > as I expected, should I be able to get a super-fast NFS share?
My first theory would be: NFS forces "commit to disk" before returning the reply to the matching NFS request... and tmpfs may likely try to write the matching pages to the disk and then returns after the write completes. Beyond the theory: Which kind of NFS requests are slow - data reads, data writes or inode create/delete/changes ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
