Virtual processor usage wrong?
Hi,
(No AIX section?)
I have been collecting load data from uptime on our AIX and Linux servers following Earl Jew's CSoW measurements in his Starting Tactic presentation.
Sadly, lpar2rrd shows at least double the amount of virtual processors as my/Earl's calculations, which is frustrating as I have a hard time getting my capacity planning paradigm through.
I had a look at lpar2rrd.pl and found this:
sub get_smt_details {
my ( $wrkdir, $server, $lpar ) = @_;
my $server_space = $server;
my $lpar_space = $lpar;
# check if exists data/server/hmc/lpar/cpu.txt where the OS agent saves SMT
But all the cpu.txt file I have found are wrong:
# cat cpu.txt
4
On the actual LPAR:
# smtctl
This system is SMT capable.
This system supports up to 8 SMT threads per processor.
SMT is currently enabled.
SMT boot mode is set to enabled.
SMT threads are bound to the same virtual processor.
proc0 has 8 SMT threads.
Bind processor 0 is bound with proc0
Bind processor 1 is bound with proc0
Bind processor 2 is bound with proc0
Bind processor 3 is bound with proc0
Bind processor 4 is bound with proc0
Bind processor 5 is bound with proc0
Bind processor 6 is bound with proc0
Bind processor 7 is bound with proc0
I think this accounts for the virtual processor graph being doubled. I'm not the greatest Perl reader though, so struggling a little bit debugging this.
I can't figure out where lpar2rrd actually try to get the SMT setting from or maybe it defaults to 4 because it can't, but I can't find that either.
Regards,
Henrik Morsing
Comments
-
Ok, I will take the silence as agreement.
How do I log a bug report? I can't find it mentioned anywhere.
Regards,
Henrik Morsing
-
sorry, responsible developer is sick, we will answer next week latest
-
Thanks Pavel, hope he/she recovers quickly.
Regards,
Henrik Morsing
-
ok, I check it our labs and it is correct, when there is 8, then cpu.txt contains 8, when 4 then 4.
what are your lpar2rrd server and the OS agent versions?
-
Hi Pavel,
I'm confused about the OS agent side, from the documentation, it uses an API. I don't think we have installed any agents.
OS, well, HMC is V10 R2 SP1040 / MF71107. The AIX LPARs are 7.2.5.2 or 7.2.5.4. The lpar2rrd server is on 7200-05-06-2320.
Regards,
Henrik Morsing
-
I believe that info comes only from the OS agent, check on some of your LPAR where do you think cpu.txt si wrong:
rpm -qa| grep lpar2rrd
-
P.S. Just noticed all the cpu.txt files are at least six years old. It obviously can't pick-up the data for some reason.
Regards,
Henrik Morsing
-
you perahs had there an OS agent in the past
rpm -qa| grep lpar2rrd
-
Ok,
So the OS agent is only to find the SMT level? Can I define it manually somewhere?
Regards,
Henrik Morsing
-
yep, the OS agent, if you no longer use it then you can edit cpu.txt manually
-
Hi Pavel,
I have just checked all our systems and we don't have the agent installed anywhere.
Regards,
Henrik Morsing
-
Hi Pavel,
The problem with writing this manually is LPM. I don't think it will work.
Regards,
Henrik Morsing
-
use the OS agents tiom keep it fresh and to get further OS based metrics https://lpar2rrd.com/agent.php
-
Thanks,
I'm planning to implement the agents.
Regards,
Henrik Morsing
Howdy, Stranger!
Categories
- 1.6K All Categories
- 36 XORMON NG
- 25 XORMON
- 146 LPAR2RRD
- 12 VMware
- 15 IBM i
- 2 oVirt / RHV
- 4 MS Windows and Hyper-V
- Solaris / OracleVM
- XenServer / Citrix
- Nutanix
- 6 Database
- 2 Cloud
- 10 Kubernetes / OpenShift / Docker
- 121 STOR2RRD
- 18 SAN
- 7 LAN
- 17 IBM
- 3 EMC
- 12 Hitachi
- 5 NetApp
- 15 HPE
- Lenovo
- 1 Huawei
- 1 Dell
- Fujitsu
- 2 DataCore
- INFINIDAT
- 3 Pure Storage
- Oracle