No, I have multiple client systems, so I do need the locks to go to the NetApp.
Edward.
-----Original Message----- From: Duncan Greenwood [mailto:duncan.greenwood@btinternet.com] Sent: 12 December 2002 22:56 To: Edward Hibbert; toasters@mathworks.com Subject: Re: NFS Lock Performance
You don't say whether you have multiple client systems mounting the share, or just a single client with multiple processes contending for locks.
In the latter situation and depending on your client o/s, you may be able to dispense with the lock manager altogether and use local kernel locks instead, using the "llock" option to the NFS mount command.
rgds,
D #
----- Original Message ----- From: "Edward Hibbert" EH@dataconnection.com To: toasters@mathworks.com Sent: Thursday, December 12, 2002 10:13 PM Subject: NFS Lock Performance
I'm hitting a filer very hard with NFS lock/unlock calls. Although the ops/second is still comfortably below what I've seen it do before (with
more
read/write ops), I'm seeing it occasionally take many seconds to return
from
a non-blocking lock attempt, or from an unlock call.
I theorise based purely on ignorance that I might be soaking the lock manager. Is there any tuning I can do (e.g. add more threads)?
Regards,
Edward Hibbert.
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 13/11/2002