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 performan
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
proje
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
On 13 dec 2010, at 10:50, 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*'
That should work, I have used it without problem and the "zon
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
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 zone.max
