Blogs Classifieds Downloads FlashChat Gallery Googlemap Invite Friends Links Projects Reviews Wiki
 


Welcome to the pSeries Tech Forums, our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software.

You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments.

Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community.

Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Our Sponsors
Want to advertise?  


Reply
 
LinkBack Thread Tools
  #1  
Old August 25th, 2006
dthacker's Avatar
dthacker Offline
Cat Herder and Penguin Wrangler
 
Join Date: June 2006
Location: Omaha, Nebraska USA
Posts: 86
Send a message via Yahoo to dthacker
Confusing NMON Results

Configuration is: p570, 4 physical CPU's
The LPAR is question is configured:
Processor Mode: Shared
Processing Units: Min=2 Desired=2 Max=3
Virtual Processors: Min=8 Desired=8 Max=12
Uncapped, Weight 180

Code:
──nmon-v10r───g=disk-Groups──────Host=omni-res───────Refresh=2 secs───14:27.36──────────────────────────────
┌─CPU-Utilisation-Small-View────────────EntitledCPU=2.00 UsedCPU 2.829─────────────────────────────────┐
│Logical                    0----------25-----------50----------75----------100                            │
│CPU User%  Sys% Wait% Idle%|           |            |           |            |                            │
│  0  12.5  13.0   0.0  74.5|UUUUUUssssss      >                              |                            │
│  1   0.0   0.0   0.0 100.0|           >                                     |                            │
│  2  25.5  10.5   0.0  64.0|UUUUUUUUUUUUsssss                  >             |                            │
│  3   5.1   0.0   0.0  94.9|UU                       >                       |                            │
│  4  16.0  12.5   0.0  71.5|UUUUUUUUssssss   >                               |                            │
│  5   0.0   5.4   0.0  94.6|ss      >                                        |                            │
│  6  27.5  11.0   0.0  61.5|UUUUUUUUUUUUUsssss>                              |                            │
│  7   0.0  11.0   0.0  89.0|sssss    >                                       |                            │
│  8  19.0  11.5   0.0  69.5|UUUUUUUUUsssss   >                               |                            │
│  9   0.0   0.0   0.0 100.0|     >                                           |                            │
│ 10  10.0  15.9   0.0  74.1|UUUUsssssss      >                               |                            │
│ 11   0.0   5.0   0.0  95.0|ss      >                                        |                            │
│ 12  41.3   8.5   0.0  50.2|UUUUUUUUUUUUUUUUUUUUssss >                       |                            │
│ 13   0.0   0.0   0.0 100.0|     >                                           |                            │
│ 14  18.5  19.0   0.0  62.5|UUUUUUUUUsssssssss>                              |                            │
│ 15   0.0   5.0   0.0  95.0|ss    >                                          |                            │
│Logical/Physical Averages  +-----------|------------|-----------|------------+                            │
│Log  11.1   8.0   0.0  80.9|UUUUUssss                                        |                            │
│Phy  47.8  38.2   0.0  14.1|UUUUUUUUUUUUUUUUUUUUUUUsssssssssssssssssss       |                            ││Entitlement Used=141.4%    +-----------|------------|-----------|------------+                            │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────
  1. What does the Entitled CPU measurement refer to? The desired processing units?
  2. Why are physical processors 80% busy, yet logical processors are 80% idle?
  3. Why do I have 16 logical processors? I thought I should have 8.
  4. Could someone please explain the difference between a virtual processor and a logical processor?
I have folks in suits thinking we need more CPUs. If you run a day's worth of stats through nmon_analyzer, the CPU load never goes over 30%. I've been back through my LPAR class books trying to account for the difference between logical and physical processors, but haven't located anything.

TIA Dave
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #2  
Old August 28th, 2006
astralvoid's Avatar
astralvoid Offline
Junior Member
 
Join Date: August 2006
Location: Charleston, WV
Posts: 22
Re: Confusing NMON Results

I'll try to help if I can.

1. The EntitledCPU refers to your LPAR's allocated CPUs upon LPAR startup. Generally this will be your Desired CPU amount.

2. Physical processors refer to your allocation CPU units. This refers to your UsedCPU units. Logical processors refer to the virtual CPUs that you've allocated.

3. You have 16 logical processors because SMT (Simultaneous Multi-Threading) is enabled on your requested 8 Virtual CPUs. You can enable/disable this with the smtctl -m on|off command. smtctl without args will show your current settings.

4. You can probably figure out this answer with the answers already given, but Virtual Processors are manually allocated units that you allocate during your LPAR definition. Logical CPUs will be either the same number as Virtual CPUs or 2x, depending on your SMT setting.

With regards to whether you need more CPU's, remember that you only have 4 physical CPUs. With your currently defined CPU allocations, I would imagine that you will be doing a LOT of context switching between processor time slices. My recommendation would be to lower your Virtual CPUS setting to 4 to coincide with the physical processors you have. This should reduce the amount of context switching due to there being so many Logical processors context changes during each CPU slice. You should see a better response time with this. If your application has a very heavy load of CPU intensive jobs, you may see a larger performance increase by disabling SMT (smtctl -m off) . This can be changed dynamically, so you may want to test which works best for you.


I hope this helps!! I know how complex these systems can become!
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #3  
Old August 28th, 2006
dthacker's Avatar
dthacker Offline
Cat Herder and Penguin Wrangler
 
Join Date: June 2006
Location: Omaha, Nebraska USA
Posts: 86
Send a message via Yahoo to dthacker
Re: Confusing NMON Results

Thanks for the reply. As a follow up question, is there a certain level of context switches that is considered optimal?

Dave
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #4  
Old August 28th, 2006
astralvoid's Avatar
astralvoid Offline
Junior Member
 
Join Date: August 2006
Location: Charleston, WV
Posts: 22
Re: Confusing NMON Results

Based on everything I've read, there are baselines, but primarily, it is a trial and error thing.

The baseline in the documents I have state:

Uncapped Partitiions: increase # of VPU up to number of Physical processors in shared pool. (ie. 4) -- Start with 25% more than minimum and tune based on performance.

Capped PArtitions: Use minimum # VPU and monitor performance.

Bascially, each VPU is potentially worth 10ms of physical processing time. So if you allocate 1.0 CPU, and you have 1 VPU defined, the single VPU gets the full 10ms of processing time. Each additional VPU you add will split this time further, so 2VPU means each processor will get only 5 ms each. As you can see, a large number of VPUs will cause the processors to 'context switch' so much that there is very little time for real application processing.

1.0 CPU = 10ms 'real physical' processor time, thus 2.0CPU means we could have 2 VPUs with a full 10ms each since 2.0 * 10ms = 20ms or 4 VPUs with 5ms each.


I hope this makes a little sense. It's quite confusing, but once you grasp the concepts, it becomes...somewhat clearer than mud.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Reply

Bookmarks

These are the 100 most searched terms
Search Cloud
0042-001 0042-001 nim 0513-001 the system resource controller daemon is not active 0513-001 the system resource controller daemon is not active. 0514-061 0514-061 cannot find a child device 0514-061 cannot find a child device. 0516-787 0516-787 extendlv 0516-787 extendlv: maximum allocation for logical volume 110000ac aa00e1f3 aio aix aix aio aix freeware aixif_arp_dup_addr b150f22a b181fb53 ba010004 c1001020 d133c002 dacnone dcb47997 dlpar fcp_array_err6 fget_config gnu tar aix gsclvmd gtar aix hi yall hmc root password hmc vmware hscl05db ibm p6 ibm p6 520 libpopt aix libpopt.a libpopt.a(libpopt.so.0) is needed by rsync-2.6.2-1 migratelv mksysb navisphere agent nim server pseries pseriestech rsync aix sc_disk_err4 scan_error_chrp vio server websm xhost file ... powered by Simple Search Cloud


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
Nmon data to be analyise harms AIX for POWER Systems 7 August 1st, 2006 23:38



Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Powered by vbWiki Pro 1.3 RC5. Copyright ©2006-2007, NuHit, LLC

vBulletin Skin developed by: vBStyles.com


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50