It is not important. NVRAM cache allows fast NFS response, whichs lift 35 MB
bottleneck (syncronous writes) and
makes real IO to be a real bottleneck (so NFS shows the same speed as, say,
iSCSI).

NFS problem is in syncronous writes - NFS is stateless (even new) in
general, so when you write, you must wait until data are on the physical
disk (else you are not garanteed that data pass thru, server can reboot
before data went to the disk and you never know about it).

(I am not sure about NFS4, through).

Btw, don't forget to configure a jumbo frames on the network.


----- Original Message -----
From: "Kevin Closson" <kevinc@(protected)>
To: <suse-oracle@(protected)>
Sent: Thursday, September 21, 2006 1:16 PM
Subject: RE: [suse-oracle] Re: [SPAM] Re: [suse-oracle] disk read and
processes


>>>
>>>NFS server can write fast ONLY if server have
>>>battery-protected cache and works in write-back mode.

Correct, but the NVRAM cache is finite and when it has to
checkpoint it throttles writes from the NFS clients
substantially.



--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting



--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting