Re: [zones-discuss] Zone Resource Management Issue.

2010-12-15 Thread Jeff Victor

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 to locked memory usage in kstat o/p
Older versions of some memory-measurement tools counted shared memory multiple 
times: once for each process that was using the shmem. That might explain the 
report of 13G. 

--JeffV

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Zone Resource Management Issue.

2010-12-14 Thread Joe Balenzano
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 have?  Is it possible the system is 
paging?  Look at vmstat output.


-Steve

On 12/13/10 10:03 PM, Ketan wrote:

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 performance 
issue due to memory .. as they are checking the memory from the   RSS 
column of prstat output for that particular zone/project which is 
larger than the locked memory as per kstat


See below output for the project

module: capsinstance: 0
name:   lockedmem_project_2009  class:project_caps
 crtime  1201534.6985509
 snaptime5612713.3006914
 usage   2147488563
 value   12335423324
 zonenameglobal




  1018253   9125M5913M   2.3%   46:44:54 1.5% project2
  3  384   23G   15G5.8%   23:11:58 0.5%default
   1020317   24G   22G8.8%   29:09:16 0.3%project1
  0   59304M 259M  0.1%   101:14:15 0.1%  system
   1013175   7737M   5615M 2.1%   16:44:21 0.0%
project3[b][/b][b][/b]

___
zones-discuss mailing list
zones-discuss@opensolaris.org



--


___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-14 Thread Ketan
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


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-14 Thread Ketan
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
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-14 Thread Ketan
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
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-14 Thread Ketan
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
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-13 Thread Henrik Johansson
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-locked-memory  what would be the best way 
 as if i try to use prstat -Z the RSS column shows 10G being used the by the 
 zone1 though max-locked-memory is set to 4G only

RSS memory does not mean that it is locked just that it is present in memory, 
with your setting you could have any amount of non-locked, non-share memory. I 
would have a look at the larger processes with using pmap with the x option, 
looking at the locked column and sizes.

If you want to limit the use of physical memory for the zone, try using rcapd 
(it does not limit the usage but tries to enforce it asynchronously by pushing 
out pages to disk).

Regards

Henrik
http://sparcv9.blogspot.com

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Zone Resource Management Issue.

2010-12-13 Thread Ketan
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 very slow and they are getting memory related 
errors  

module: capsinstance: 0
name:   lockedmem_project_  class:project_caps
usage   2488147563
value   36335423324
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-13 Thread Henrik Johansson
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 problem and the zonestat script by 
Jeff also uses this.

 
 but with this command the usage is very less  as reported by the application 
 user which says that db is doin very slow and they are getting memory related 
 errors  
 
 module: capsinstance: 0
 name:   lockedmem_project_  class:project_caps
   usage   2488147563
   value   36335423324

Are you saying the zone has more memory locked than kstat shows? Have you 
verified that the memory is in fact locked by using pmap as I suggested 
earlier? Have you tried to enable logging for the resource controls with 
rctladm to see which limits are limiting the database?

Regards

Henrik
http://sparcv9.blogspot.com
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-13 Thread Steve Lawrence

 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 command the usage is very less  as reported by the application 
user which says that db is doin very slow and they are getting memory related 
errors

module: capsinstance: 0
name:   lockedmem_project_  class:project_caps
 usage   2488147563
 value   36335423324



___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-13 Thread Ketan
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 
project .. 


And i have not enabled logging yet ..
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Resource Management Issue.

2010-12-13 Thread Ketan
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 performance issue due to memory .. as they 
are checking the memory from the   RSS column of prstat output for that 
particular zone/project which is larger than the locked memory as per kstat 

See below output for the project 

module: capsinstance: 0
name:   lockedmem_project_2009  class:project_caps
crtime  1201534.6985509
snaptime5612713.3006914
usage   2147488563
value   12335423324
zonenameglobal




 1018253   9125M5913M   2.3%   46:44:54 1.5% project2
 3  384   23G   15G5.8%   23:11:58 0.5%default
  1020317   24G   22G8.8%   29:09:16 0.3%project1
 0   59304M 259M  0.1%   101:14:15 0.1%  system
  1013175   7737M   5615M 2.1%   16:44:21 0.0%project3[b][/b][b][/b]
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org