NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Dewdman42
May 21, 2012Virtuoso
NFS Tunning? - some benchmarks
I ran some benchmarks to compare various modes of file sharing, and got some surprising results. My intution was that NFS would be the best option, but its performance was off (see below). So do...
Dewdman42
May 22, 2012Virtuoso
hmm, no what I mean to say is that the benchmark results from NFS were better than AFP and SMB in terms of large block size, but worse in terms of 4k blocks. If I can tune how the smaller blocks are handled while also keeping the nice high numbers of the large blocks, then it would out perform both AFP and SMB.
AFP and SMB also seem to have some delay overhead related to browsing directories. This is undoubtedly because they are writing odd ball hidden files related to resource forks, trash cans and such things. AFP always has a long delay before opening a folder for the first time Finder, but then after that its faster. In the past I have experienced similar delays with SMB, even from windows clients. When I was using windows clients before, I used to use FTP for large transfers because it would always out perform SMB by a long shot. Not sure if Windows explorer was causing the bottleneck or SMB.
when I use AFP to access the NAS, I see deskop and trash can files being created and/or maintained. Not sure what is in there, but I'm assuming its related to resource forks, icons, etc. That means overhead, so feels slower. I believe NFS avoids that, but granted, resource forks are probably lost to NFS shares. For Mac users, care has to be exercised to avoid losing resource forks from mac files with NFS.
In any case, NFS has a buzzillion options for tuning this or that, so just wondering if anyone has some suggestions along those lines. Otherwise I will sick with AFP and just endure the long load time for browsing directories
AFP and SMB also seem to have some delay overhead related to browsing directories. This is undoubtedly because they are writing odd ball hidden files related to resource forks, trash cans and such things. AFP always has a long delay before opening a folder for the first time Finder, but then after that its faster. In the past I have experienced similar delays with SMB, even from windows clients. When I was using windows clients before, I used to use FTP for large transfers because it would always out perform SMB by a long shot. Not sure if Windows explorer was causing the bottleneck or SMB.
when I use AFP to access the NAS, I see deskop and trash can files being created and/or maintained. Not sure what is in there, but I'm assuming its related to resource forks, icons, etc. That means overhead, so feels slower. I believe NFS avoids that, but granted, resource forks are probably lost to NFS shares. For Mac users, care has to be exercised to avoid losing resource forks from mac files with NFS.
In any case, NFS has a buzzillion options for tuning this or that, so just wondering if anyone has some suggestions along those lines. Otherwise I will sick with AFP and just endure the long load time for browsing directories
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!