GNOME System Monitory says no mem consumed by ZFS??
837971Feb 8 2011 — edited Feb 8 2011Hi, I'm guessing there is probably a simple answer to this but Google and I haven't found it.
With OpenSolaris svn_111b, the GNOME System Monitor would show almost all memory consumed. (By ZFS cache...a good thing.)
With Solaris Express svn_151a, System Monitor shows <1gb (out of 16gb) consumed.
Would I be correct in assuming that ZFS cache is no longer counted in the System Monitor, but ZFS is still using almost all available memory (hopefully)?
The reason for concern is that with svn_111b, I was getting a reliable 90 MB/s transfer over SMB (with Solaris as Samba server), without even jumbo frames. But now, on the same server and network config but with a clean install of svn_151a and minimal tweaking, I'm getting terrible performance at about 3 to 10 MB/s.
(I've posted the performance problem specifically as a separate post, so as not to double-post I don't want to dwell on that here - this is just about the System Monitor / ZFS cache question.)
Thanks!!
-Jim
Specs, if it matters for this question:
Machine:
- 2*4-core Xeons
- 16gb ECC RAM
- Onboard e1000g NIC
- 20 hot-swap bays
- cooling out the wazoo
rpool:
- mirrored 30gb SSDs
Pool "zp3" config:
- LSI SAS1068E-R c9 HBAs
- 6 * 3-way mirrors, 1tb, 7200 RPM enterprise-class SATA
- 2 hot spares
- 2 * 30gb SSD for L2ARC
Pool "zp3" settings:
zp3 version 5 -
zp3 sync disabled local
zp3 com.sun:auto-snapshot true local
zp3 recordsize 128K default
zp3 utf8only on -
zp3 normalization formD -
zp3 casesensitivity insensitive -
zp3 encryption off -
zp3 compression on local
zp3 compressratio 1.07x -
zp3 dedup off local
zp3 logbias throughput local
zp3 used 4.21T -
zp3 usedbysnapshots 311G -
zp3 usedbydataset 3.90T -
zp3 usedbychildren 8.78G -
zp3 usedbyrefreservation 0 -
zp3 available 1.04T -
Type of data and access:
- Mostly large media files (DNG photos, large photoshop project files, high bitrate 1080p video, 32-bit/96khz audio, etc.)
- Plenty of small "office" data files too, but of secondary importance.
- Low usage. Typically accessed by one CIFS/SMB client - and one application - at a time. Needs throughput, not IOPS.
Edited by: user13689618 on Feb 8, 2011 12:48 PM (Oops, used ">" as list bullets.)