01-10-2019
thanks for looking.
turns out it was really dopey, it's about the size of the window that topas is running in. it apparently thinks 24 rows isn't enough to show more than 2 CPUs. stretch it to 48 and it shows all the CPUs, consistently across all the LPARs I tried.
Bad design ? They say the window is scrollable, so why display misleading data...
Curses, foiled again !
This User Gave Thanks to maraixadm For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there an easy way in Solaris to count the number of processors? (2 Replies)
Discussion started by: hshapiro
2 Replies
2. UNIX for Dummies Questions & Answers
We have purchased four intels xeon processors
Intel® Xeon® Processor E7530 (12M Cache, 1.86 GHz, 5.86 GT/s Intel® QPI) with SPEC Code(s) SLBRJ
As per the specification each cpu has 6 cores therefore we have 24 cores (considering 4 cpus).
Now how would i calculate the number of vcpus that can... (1 Reply)
Discussion started by: pinga123
1 Replies
3. AIX
I have a number of LPARs on one P520. All LPARs are running 5.3 and I observe the following:
On some LPARs the number of CPUs found do not match between topas and mpstat.
Server 1:
$ mpstat
System configuration: lcpu=4 ent=0.2 mode=Uncapped
cpu min maj mpc int cs ics rq ... (1 Reply)
Discussion started by: petervg
1 Replies
4. Red Hat
Hi,
I am observing high load average on RHEL5 server and need to check the number of core processors available on the box to give me a bigger picture on whether or not I should be worried.
I have always checked the physical count quite simply.....
# grep 'physical id' /proc/cpuinfo |... (10 Replies)
Discussion started by: Duffs22
10 Replies
5. Red Hat
Hello,
sysinfo throws out below 3 CPU counts. Can anyone help me understand what each of these means?
CPU Count Socketed is 2
CPU Count Physical is 8
CPU Count Virtual is 16
First one seems obvious. However, I wonder how there can be 8 Physical CPUs, if... (2 Replies)
Discussion started by: hnhegde
2 Replies
6. AIX
Hello,
I am looking into virtualizing AIX 7.1 on our p7 machine that already has AIX 7.1 installed on it. I have a few questions about them:
1) In order to gain LPAR functionality, do I need to purchase PowerVM software?
2) I read that LPARs are managed from locally attached graphical... (1 Reply)
Discussion started by: bstring
1 Replies
7. AIX
Hello Everyone,
i got a question in AIX. How can i track the communication between LPARs.
i mean how can we find if a program/account trying to access a directory/file inside AIX LPAR or from another LPAR ?
if some one is trying to access our LPAR. where can i track those info? or a outside... (5 Replies)
Discussion started by: System Admin 77
5 Replies
8. AIX
Hi Folks,
I am working on a task - Cloning the OS from fullSystem partition to 3 new LPAR's using alt_disk_install.
I just wanted to clarify my steps here.
1. alt_disk_install -CBO hdisk1 and rename it to alt1
2. alt_disk_install -CBO hdisk2 and rename it to alt2
3. alt_disk_install... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
9. AIX
Hi,
I have a p520 with 2 cpus and 10gb of ram.Is it sufficient enough to create 2 lpars.What other things we have to check. (2 Replies)
Discussion started by: sekar52
2 Replies
10. AIX
To get only the cpu info from the topas command terminal.
CPU User% Kern% Wait% Idle% Physc Entc
ALL 2.3 4.4 0.0 93.3 0.07 7.7
I tried some thing like this but did not work
topas << done
grep "ALL"
q
done
Can someone help me in this. (5 Replies)
Discussion started by: rpm120
5 Replies
LEARN ABOUT CENTOS
perf-trace
PERF-TRACE(1) perf Manual PERF-TRACE(1)
NAME
perf-trace - strace inspired tool
SYNOPSIS
perf trace
DESCRIPTION
This command will show the events associated with the target, initially syscalls, but other system events like pagefaults, task lifetime
events, scheduling events, etc.
Initially this is a live mode only tool, but eventually will work with perf.data files like the other tools, allowing a detached record
from analysis phases.
OPTIONS
-a, --all-cpus
System-wide collection from all CPUs.
-e, --expr
List of events to show, currently only syscall names. Prefixing with ! shows all syscalls but the ones specified. You may need to
escape it.
-o, --output=
Output file name.
-p, --pid=
Record events on existing process ID (comma separated list).
-t, --tid=
Record events on existing thread ID (comma separated list).
-u, --uid=
Record events in threads owned by uid. Name or number.
-v, --verbose=
Verbosity level.
-i, --no-inherit
Child tasks do not inherit counters.
-m, --mmap-pages=
Number of mmap data pages. Must be a power of two.
-C, --cpu
Collect samples only on the list of CPUs provided. Multiple CPUs can be provided as a comma-separated list with no space: 0,1. Ranges
of CPUs are specified with -: 0-2. In per-thread mode with inheritance mode on (default), Events are captured only when the thread
executes on the designated CPUs. Default is to monitor all CPUs.
--duration: Show only events that had a duration greater than N.M ms.
--sched: Accrue thread runtime and provide a summary at the end of the session.
-i --input Process events from a given perf data file.
SEE ALSO
perf-record(1), perf-script(1)
perf 06/30/2014 PERF-TRACE(1)