On Fri, Oct 31, 2008 at 9:30 PM, zhihui Chen <[EMAIL PROTECTED]> wrote:
> intel7# vmstat 2
> kthr memory page disk faults cpu
> r b w swap free re mf pi po fr de sr rm s0 s1 -- in sy cs us sy
> id
> 5 0 0 7588092 5866084 8 163 7 6 18 0 124 -20625 12 -0 0 3205 194187 50279
> 10 3 87
> 0 0 0 7935004 6799272 7 45 0 0 0 0 0 0 9 0 0 431 228 390 0 0
> 100
> 0 0 0 7934852 6799140 0 5 0 0 0 0 0 0 0 0 0 417 236 341 0 0
> 100
> intel7# java -d64 -Xms8g -Xmx8g -version
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
Memory allocations place a reservation against swap. If vmstat's swap
column says you have less than 8 GB of swap available, you will not be
able to reserve 8 GB of memory. Note that even if the system shows 1
TB in the free column, memory allocations will fail if the swap column
is smaller than what you are trying to allocate. The swap column shows
the amount of RAM + swap device space that has not already been
reserved.
I'm not sure why the ::memstat and vmstat are in disagreement on the
size of the free list. My understanding is that they should be the
same. According to vmstat(1M):
memory Report on usage of virtual and real memory.
swap available swap space (Kbytes)
free size of the free list (Kbytes)
Perhaps the ZFS ARC has changed the usefulness of the ::memstat
output. You may get a more focused audience on perf-discuss.
--
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
opensolaris-discuss mailing list
[email protected]
