In principal it does not surprise me that it is much slower on your OS X
client than on your Linux or Windows clients. When you open a folder in
your Linux or Windows file browser all they will need to do is request a
file listing. On the other hand an OS X client will read the resourse fork
I will test the results from both Windows and Mac OS X clients with the
data hosted on a Windows server to measure the results. From experience,
I expect that the Mac OS X clients will still perform worse but not to
the same degree as when the data was hosted on Samba.
Turns out that we are
I would strongly suspect that the Mac OS finder is simply hammering the
file server because, in your case, it as to do 1 seperate read opertions
just to display the folder contents. Try with an NFS share, this would
identify whether the SMB support in either the client or server is
ineffecient
On Fri, 2004-05-14 at 14:22, ww m-pubsyssamba wrote:
I would strongly suspect that the Mac OS finder is simply hammering the
file server because, in your case, it as to do 1 seperate read opertions
just to display the folder contents. Try with an NFS share, this would
identify whether the
On Sat, 2004-05-15 at 03:34, Nathan R. Valentine wrote:
I will test the results from both Windows and Mac OS X clients with the
data hosted on a Windows server to measure the results. From experience,
I expect that the Mac OS X clients will still perform worse but not to
the same degree as
Hi Nathan,
all I can say is we are also testing Mac OS X with Samba (on Solaris)
and with slightly more typical numbers of files per directory are not seeing
any simliar issues.
In principal it does not surprise me that it is much slower on your OS X
client than on your Linux or Windows
