Date: Wed, 19 May 2010 10:46:46 +0200 From: Matthias Gamsjager <mgamsjager@gmail.com> To: Arnaud Houdelette <tzim@tzim.net> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS Recordsize tuning & transmission (bittorent daemon) Message-ID: <AANLkTilnb_F-mi8ak42Ql3Aipxrn52dddFQNPX9en4_J@mail.gmail.com> In-Reply-To: <4BF3A0DD.4080404@tzim.net> References: <4BF3A0DD.4080404@tzim.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > ZFS recordsize on both pools are default (128k). But as transmission > bittorrent client has no write (nor read) cache, it could mean that data is > written is smaller chunks during download. Could this lead to data being > stored in many not-full records ? Does those unfull records would have to be > read as whole (128k) during the move, which would explain the above > difference on read/write ? > > I'm just making assumptions here, as my understanding of internals of ZFS is > limited. Some insights would be appreciated. > Well ZFS does not write immediately but waits couple of seconds and write them in 1 single write operation. could you give more info about what freebsd version do you use, hardware used, zfs parameters in /boot/loader.conf and zfs info like compression etc... did you test your pool with Iozone to see if it performance as it should?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTilnb_F-mi8ak42Ql3Aipxrn52dddFQNPX9en4_J>