Interesting, but what does it mean :)
The x4500 for mail (NFS vers=3 on ufs on zpool with quotas):
# ./zilstat.ksh
N-Bytes N-Bytes/s N-Max-Bytes/s B-Bytes B-Bytes/s B-Max-Bytes/s
376720 376720 376720 1286144 1286144 1286144
419608 419608 419608 1368064 1368064 1368064
555256 555256 555256 1732608 1732608 1732608
538808 538808 538808 1679360 1679360 1679360
626048 626048 626048 1773568 1773568 1773568
753824 753824 753824 2105344 2105344 2105344
652632 652632 652632 1716224 1716224 1716224
Fairly constantly between 1-2MB/s. That doesn't sound too bad though.
It's only got 400 nfsd threads at the moment, but peaks at 1024.
Incidentally, what is the highest recommended nfsd_threads for a x4500
anyway?
Lund
Marion Hakanson wrote:
> The zilstat tool is very helpful, thanks!
>
> I tried it on an X4500 NFS server, while extracting a 14MB tar archive,
> both via an NFS client, and locally on the X4500 itself. Over NFS,
> said extract took ~2 minutes, and showed peaks of 4MB/sec buffer-bytes
> going through the ZIL.
>
> When run locally on the X4500, the extract took about 1 second, with
> zilstat showing all zeroes. I wonder if this is a case where that
> ZIL bypass kicks in for >32K writes, in the local tar extraction.
> Does zilstat's underlying dtrace include these bypass-writes in the
> totals it displays?
>
> I think if it's possible to get stats on this bypassed data, I'd like
> to see it as another column (or set of columns) in the zilstat output.
>
> Regards,
>
> Marion
>
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
--
Jorgen Lundman | <lund...@lundman.net>
Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work)
Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell)
Japan | +81 (0)3 -3375-1767 (home)
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
