search for: arc_adjust

...e80005c3a70 ss: 30 fffffe80005c3870 unix:die+eb () fffffe80005c3970 unix:trap+14f9 () fffffe80005c3980 unix:cmntrap+140 () fffffe80005c3aa0 zfs:buf_hash_remove+54 () fffffe80005c3b00 zfs:arc_change_state+1bd () fffffe80005c3b70 zfs:arc_evict_ghost+d1 () fffffe80005c3b90 zfs:arc_adjust+10f () fffffe80005c3bb0 zfs:arc_kmem_reclaim+d0 () fffffe80005c3bf0 zfs:arc_kmem_reap_now+30 () fffffe80005c3c60 zfs:arc_reclaim_thread+108 () fffffe80005c3c70 unix:thread_start+8 () syncing file systems... done dumping to /dev/md/dsk/swap, offset 644874240, content: kernel > $c buf_hash_rem...

Would someone "in the know" be willing to write up (preferably blog) definitive definitions/explanations of all the arcstats provided via kstat? I''m struggling with proper interpretation of certain values, namely "p", "memory_throttle_count", and the mru/mfu+ghost hit vs demand/prefetch hit counters. I think I''ve got it figured out, but

Running an mmap-intensive workload on ZFS on a X4500, Solaris 10 11/06 (update 3). All file IO is mmap(file), read memory segment, unmap, close. Tweaked the arc size down via mdb to 1GB. I used that value because c_min was also 1GB, and I was not sure if c_max could be larger than c_min....Anyway, I set c_max to 1GB. After a workload run....: > arc::print -tad { . . . ffffffffc02e29e8