Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support How to fix the CPU bound issues on AIX? Post 302860905 by System Admin 77 on Monday 7th of October 2013 01:28:31 PM
Old 10-07-2013
@bakunin

Thank you very much for your analysis. Appreciate your time. This really helps many people like me.


In my Case,
I understand that, i need to increase physical processors (Desired) from HMC. But i see suddenly the CPU usage went down, today it is


Code:
System configuration: lcpu=10 mem=24576MB ent=1.00

 kthr          memory                         page                       faults                 cpu
------- --------------------- ------------------------------------ ------------------ -----------------------
  r   b        avm        fre    re    pi    po    fr     sr    cy    in     sy    cs us sy id wa    pc    ec
  9   0    2568885      36174     0     0     0     0      0     0   121   1184   703  1  1 97  0  0.03   3.5
 13   0    2568885      36172     0     0     0     0      0     0    42    906   522  1  1 98  0  0.03   2.7
  5   0    2568885      36172     0     0     0     0      0     0    10    814   485  0  1 99  0  0.02   1.7
  5   0    2568885      36172     0     0     0     0      0     0     8    815   492  0  1 99  0  0.02   1.7
  5   0    2568885      36169     0     0     0     0      0     0    11   2153   482  1  2 97  0  0.03   3.4

I know that, a particular JVM or DB process consumed lot of CPU (by ruuning topas)
But am not sure, how to tune it. (*Not sure why it went down)

Another Question,

How can we set/decide the number of Virtual CPUs in any LPAR. I mean on what basis ?
in my case,
1 physical --ent
5 virtual ==>> 10 logical CPU

Please give your ideas.

Moderator's Comments:
Mod Comment edit by bakunin: changed "ICODE"-tags to "CODE"-tags. It is easier to read that way.

Last edited by bakunin; 10-08-2013 at 09:22 AM..
 

9 More Discussions You Might Find Interesting

1. AIX

AIX 5.3 Issues

We are planning to move to AIX 5.3 and we would like to know if someone has had any 'bad' experiences with it. We have a 32PE p690 Regatta and currently we are running the latest AIX 5.2 with the latest patches. Has anyone any interesting points to mention when transitioning to AXI 5.3? Is... (1 Reply)
Discussion started by: miket
1 Replies

2. AIX

If the AIX need reboot after install fix pack or APAR?

After install fix pack or APAR, if aix need reboot? if not, do we need stop database and all applications before we install fix pack or APAR? (3 Replies)
Discussion started by: rainbow_bean
3 Replies

3. AIX

IY17981 fix required for aix 4.3.3 to aix 5L migration but not found

Hi, redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages. - My system is ML11 : oslevel –r 4330-11 - But xlC.rte is on wrong version : lslpp -L xlC.rte xlC.rte ... (3 Replies)
Discussion started by: astjen
3 Replies

4. AIX

AIX filter Issues

Hi, I want to print from AIX 5.3/6.1 using 'pr' preprocessing filter and 'PCL' print file type. Steps: 1. Smitty 2. Print Spooling 3. Create a print queue(remote->Generic) 4. change the attributes for that print queue. 5. Change print file type to PCL and... (1 Reply)
Discussion started by: meeraramanathan
1 Replies

5. AIX

How to install AIX Fix Pack 5300-06-06-0811

Hi All, I have this fix for AIX (5300-06-06-0811) and i need to install it. How can i do this? What are the prerequisites for this fix? Thanks (1 Reply)
Discussion started by: lucaxvu
1 Replies

6. AIX

APAR fix on AIX 53tl9

We have tried to install an APAR fix IZ20298 on a AIX test server. It is requiring a base level of bos.adt.prof of 5.3.0.0 I cannot find this file anywhere. I fould 5.3.0.1 and it still will not install without the base install. Any ideas where I can find bos.adt.prof 5.3.0.0? (1 Reply)
Discussion started by: daveisme
1 Replies

7. AIX

AIX CPU use

Hi Could somebody explain me how AIX is using CPU?? For example when we have 2 processors system is giving all task to one of them till 100% is used ?? Or it's depend on configuration or anything else ?? Best regards enda (3 Replies)
Discussion started by: enda
3 Replies

8. AIX

AIX Fix Pack update

Hi All, i'm try to update my aix 6100.06.05 to 6100.07.00. i download the 4,5 GB of FixPack buy i don't have a required package (devices.chrp.pci.rte 6.1.7.0) This package does not exist on the fix pack (i've check in the .toc file and in the .bff files) On ibm website i see that this... (0 Replies)
Discussion started by: Zio Bill
0 Replies

9. AIX

AIX CPU waits

Guys, I have a question - when nmon reports a sizeable %CPU wait, does that mean - 1) IO operations are slowing CPU down, OR 2) paging slowing the CPU down, OR 3) one cant tell?? I thought the nmon documentation clearly suggested that CPU waits reported in nmon were from disk... (4 Replies)
Discussion started by: getback0
4 Replies
TASKSET(1)							   User Commands							TASKSET(1)

NAME
taskset - set or retrieve a process's CPU affinity SYNOPSIS
taskset [options] mask command [argument...] taskset [options] -p [mask] pid DESCRIPTION
taskset is used to set or retrieve the CPU affinity of a running process given its pid, or to launch a new command with a given CPU affin- ity. CPU affinity is a scheduler property that "bonds" a process to a given set of CPUs on the system. The Linux scheduler will honor the given CPU affinity and the process will not run on any other CPUs. Note that the Linux scheduler also supports natural CPU affinity: the scheduler attempts to keep processes on the same CPU as long as practical for performance reasons. Therefore, forcing a specific CPU affinity is useful only in certain applications. The CPU affinity is represented as a bitmask, with the lowest order bit corresponding to the first logical CPU and the highest order bit corresponding to the last logical CPU. Not all CPUs may exist on a given system but a mask may specify more CPUs than are present. A retrieved mask will reflect only the bits that correspond to CPUs physically on the system. If an invalid mask is given (i.e., one that corresponds to no valid CPUs on the current system) an error is returned. The masks may be specified in hexadecimal (with or without a leading "0x"), or as a CPU list with the --cpu-list option. For example, 0x00000001 is processor #0, 0x00000003 is processors #0 and #1, 0xFFFFFFFF is processors #0 through #31, 32 is processors #1, #4, and #5, --cpu-list 0-2,6 is processors #0, #1, #2, and #6. When taskset returns, it is guaranteed that the given program has been scheduled to a legal CPU. OPTIONS
-a, --all-tasks Set or retrieve the CPU affinity of all the tasks (threads) for a given PID. -c, --cpu-list Interpret mask as numerical list of processors instead of a bitmask. Numbers are separated by commas and may include ranges. For example: 0,5,8-11. -p, --pid Operate on an existing PID and do not launch a new task. -V, --version Display version information and exit. -h, --help Display help text and exit. USAGE
The default behavior is to run a new command with a given affinity mask: taskset mask command [arguments] You can also retrieve the CPU affinity of an existing task: taskset -p pid Or set it: taskset -p mask pid PERMISSIONS
A user can change the CPU affinity of a process belonging to the same user. A user must possess CAP_SYS_NICE to change the CPU affinity of a process belonging to another user. A user can retrieve the affinity mask of any process. SEE ALSO
chrt(1), nice(1), renice(1), sched_getaffinity(2), sched_setaffinity(2) See sched(7) for a description of the Linux scheduling scheme. AUTHOR
Written by Robert M. Love. COPYRIGHT
Copyright (C) 2004 Robert M. Love. This is free software; see the source for copying conditions. There is NO warranty; not even for MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. AVAILABILITY
The taskset command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/. util-linux August 2014 TASKSET(1)
All times are GMT -4. The time now is 01:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy