Hello all, There is a great diff between access the raw discs and through LVM, with some kind of RAID, and etc. I think you should use NFS v3, and it's hard to think that without you explicitally configure it to use v2, it using... A great diff between v2 and v3 is that v2 is always "async", what is a performance burst. Are you sure that in the new environment is not v3? In the new stable version (nfs-utils), debian is sync by default. I'm used to "8192" transfer sizes, and was the best perfomance in my tests. Would be nice if you could test another network service writing in that server.. like ftp, or iscsi. Another question, the discs are "local" or SAN? There is no concurrency?
ps.: v2 has a 2GB file size limit AFAIK. Leal. 2008/2/14, Font Bella <[EMAIL PROTECTED]>: > Hi, > > some of our apps are experiencing slow nfs performance in our new cluster, in > comparison with the old one. The nfs setups for both clusters are very > similar, and we are wondering what's going on. The details of both setups are > given below for reference. > > The problem seems to occur with apps that do heavy i/o, creating, writing, > reading, and deleting many files. However, writing or reading a large file > (as measure with `time dd if=/dev/zero of=2gbfile bs=1024 count=2000`) is not > slow. > > We have performed some tests with the disk benchmark 'dbench', which reports > i/o performance of 60 Mb/sec in the old cluster down to about 6Mb/sec in the > new one. > > After noticing this problem, we tried the user-mode nfs server instead of the > kernel-mode server, and just installing the user-mode server helped improving > throughput up to 12 Mb/sec, but still far away from the good old 60 Mb/sec. > > After going through the "Optimizing NFS performance" section of the > NFS-Howto and tweaking the rsize,wsize parameters (the optimal seems to be > 2048, which seems kind of weird to me, specially compared to the 8192 used in > the old cluster), throughput increased to 21 Mb/sec, but is still too far > from the old 60Mb/sec. > > We are stuck at this point. Any help/comment/suggestion will be greatly > appreciated. > /P > > **************************** OLD CLUSTER ***************************** > > SATA disks. > > Filesystem: ext3. > > * the version of nfs-utils you are using: I don't know. It's the most > recent version in debian sarge (oldstable). > > user-mode nfs server. > > nfs version 2, as reported with rpcinfo. > > * the version of the kernel and any non-stock applied kernels: 2.6.12 > * the distribution of linux you are using: Debian sarge x386 on Intel Xeon > processors. > * the version(s) of other operating systems involved: no other OS. > > It is also useful to know the networking configuration connecting the hosts: > Typical beowulf setup, with all servers connected to a switch, 1Gb network. > > /etc/exports: > > /srv/homes 192.168.1.0/255.255.255.0 (rw,no_root_squash) > > /etc/fstab: > > server:/srv/homes/user /mnt/user nfs rw,hard,intr,rsize=8192,wsize=8192 0 0 > > **************************** NEW CLUSTER ***************************** > > SAS 10k disks. > > Filesystem: ext3 over LVM. > > * the version of nfs-utils you are using: I don't know. It's the most > recent version in debian etch (stable). > > kernel-mode nfs server. > > nfs version 2, as reported with rpcinfo. > > * the version of the kernel and any non-stock applied kernels: 2.6.18-5-amd64 > * the distribution of linux you are using: Debian etch AMD64 on Intel Xeon > processors. > * the version(s) of other operating systems involved: no other OS. > > It is also useful to know the networking configuration connecting the hosts: > Typical beowulf setup, with all servers connected to a switch, 1Gb network. > > /etc/exports: > > /srv/homes 192.168.1.0/255.255.255.0 (no_root_squash) > > mount options: > > rsize=8192,wsize=8192 > - > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- pOSix rules - To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
