SAMBA Really Slow
David Collier-Brown
davecb at canada.sun.com
Mon Feb 5 17:02:18 GMT 2001
John Supplee wrote:
> It is a MS Visual FoxPro 6.0 application.
Jackpot!
Foxpro is a database (well, sort of a database), and
needs specific settings.
Try to put its data on a share by itself, and turn
off oplocks on that share. If the data has to live
with other data, use the "veto oplocks" option
and specify the files that foxpro uses.
If you leave oplocks on for a flat-file database
like froxpro, access or the like, then
- each client will try to cache the whole database
file onto a local disk
- this cache will be invalidated as soon as a second
client starts up, and the file will have to be written
back to the server.
It's preferable to not cache the file, so foxpro will
just read the particular records it needs to update.
Now multiply this by 60-odd files and you'll see
a slight performance problem (;-))
--dave
--
David Collier-Brown, | Always do right. This will gratify
Performance & Engineering Team | some people and astonish the rest.
Americas Customer Engineering | -- Mark Twain
(905) 415-2849 | davecb at canada.sun.com
More information about the samba
mailing list