On Dec 15, 2010, at 1:18 AM, Ketan vibhu...@gmail.com wrote:
B'coz .. the application user is telling that they are recieving memory
related errors
What are the error messages?
and its responding too slow and the RSS column for that particular zone is
pretty high around 13G as compared
What is the application? How do you know if the application requested
more than 2.3GB of locked memory or not? One other thing, the T5540 has
the largest memory latency times of all the CMT servers, so you could be
seeing some of this.
Steve Lawrence wrote:
How much memory does the system
System has 128G of memory , and as per vmstat -S 1 5 o/p there is no paging
happening on the system
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
B'coz .. the application user is telling that they are recieving memory related
errors and its responding too slow and the RSS column for that particular zone
is pretty high around 13G as compared to locked memory usage in kstat o/p ...
--
This message posted from opensolaris.org
B'coz .. the application user is telling that they are recieving memory related
errors and its responding too slow and the RSS column for that particular zone
is pretty high around 13G as compared to locked memory usage in kstat o/p
--
This message posted from opensolaris.org
And Steve, is kstat -c project_caps -n 'lockedmem*' is the only way to
determine the locked memory being used by a project/process ? or there is
another way too .. and how can we co-relate it to RSS in prstat -J o/p ?
--
This message posted from opensolaris.org
Hello Ketan,
On Dec 13, 2010, at 8:35 AM, Ketan wrote:
One of our box T5440 has been configured with 5 zones and following resource
management parameters has been applied to 1 zone say zone1
zone.max-shm-memory 4G
zone.max-locked-memory 4G
so if i want to check the
Ok got it .. but still if i want to check what's current usage by a whole
zone/project for locked-memory what would be the best way .. i 'm using
kstat -c project_caps -n 'lockedmem*'
but with this command the usage is very less as reported by the application
user which says that db is doin
On 13 dec 2010, at 10:50, Ketan vibhu...@gmail.com wrote:
Ok got it .. but still if i want to check what's current usage by a whole
zone/project for locked-memory what would be the best way .. i 'm using
kstat -c project_caps -n 'lockedmem*'
That should work, I have used it without
Do you mean zone_caps? You are looking at project_caps.
On 12/13/10 01:50 AM, Ketan wrote:
Ok got it .. but still if i want to check what's current usage by a whole
zone/project for locked-memory what would be the best way .. i 'm using
kstat -c project_caps -n 'lockedmem*'
but with this
No, I 'm saying that kstat shows the locked memory for the project/zone at 2.3G
and its allocated around 8G .. and still db users are saying they are
experiencing a
performance issue very slow due to memory ..
And regarding the pmap .. i can check pmap for a process but not for zone or
Hi Steve,
I meant either zone or project .. as i 'm having issue both in zone and project
..
the issue is same .. as per kstat the locked memory is around 2.3G and the
value assigned (locked-memory ) is much larger but still application users are
complaining they are experiencing a
12 matches
Mail list logo
