Sounds not dissimilar to a problem I saw some time ago with C-ISAM files on Solaris/NetApp.

It may be related to the granularlity of file/record locking. Look at the output of nfsstat for lots of small transfers (<512B). IIRC from around 12 years ago, the original dBase locked files by flipping a bit in the .dbf file header. Other *nix derivatives (eg FoxBase on Xenix) used "proper" byte-range locking for multiprocess apps.

(... memories of when you could hang ten dumb terminals off the back of a 286 box with 1MB memory - and mention SCO in polite company ...)

If you're not sharing the files to multiple NFS clients, switch to local locking using the nolock (or similar) flag to your client mount command.

There are references to the locking strategy at: http://linux.techass.com/projects/xdb/xbasedocs/xbase_c8.html

If your app is single process then maybe switch off locking altogether.

You could also experiment with different rsize and wsize values, tcp vs. udp, etc.

hth

D #

----- Original Message ----- From: "Errol Casey" errol@nouce.net To: toasters@mathworks.com Sent: Saturday, February 07, 2004 6:06 AM Subject: Xbase database files on Netapp filers

Has anybody over come slow access to to database files on netapp filers that use xbase database files?

I'm using an application that uses this database format, and the application seems to be impacted due to NFS related or Netapp specific issues. I'm working the issue with Netapp currently but thought I would ask other netapp users as well. Thanks for any input.

http://linux.techass.com/projects/xdb/ (Documents the database library itself) -- Errol Casey errol@nouce.net

--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.576 / Virus Database: 365 - Release Date: 30/01/2004