That's because NFS adds synchronous writes to the mix (e.g. the client needs to know certain transactions made it to nonvolatile storage in case the server restarts etc). The simplest safe solution, although not cheap, is to add an SSD log device to the pool.
On 23 Jul 2010, at 08:11, "Sigbjorn Lie" <sigbj...@nixtra.com> wrote: > Hi, > > I've been searching around on the Internet to fine some help with this, but > have been > unsuccessfull so far. > > I have some performance issues with my file server. I have an OpenSolaris > server with a Pentium D > 3GHz CPU, 4GB of memory, and a RAIDZ1 over 4 x Seagate (ST31500341AS) 1,5TB > SATA drives. > > If I compile or even just unpack a tar.gz archive with source code (or any > archive with lots of > small files), on my Linux client onto a NFS mounted disk to the OpenSolaris > server, it's extremely > slow compared to unpacking this archive on the locally on the server. A 22MB > .tar.gz file > containng 7360 files takes 9 minutes and 12seconds to unpack over NFS. > > Unpacking the same file locally on the server is just under 2 seconds. > Between the server and > client I have a gigabit network, which at the time of testing had no other > significant load. My > NFS mount options are: "rw,hard,intr,nfsvers=3,tcp,sec=sys". > > Any suggestions to why this is? > > > Regards, > Sigbjorn > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
