I am simply summing the total CPU times for each CP, for my report I
keep them separate, here is an example.
CP# Cpu time Wall clock
2 198 599
1 684 599
0 758 599
----------------
1640 1797
So you are saying it's okay that CPU0 and CPU1's time > wall clock?
I don't agree with that. 1640 < 1797 okay, but the accounting is wrong!
CPUADDR=2
INTERVAL USER CONECTTM CPUVIRT CPUTOTAL
19:30:28 SYSTEM 0 0.0000 9.3340
19:30:28 UNIPROD 599 181.4350 188.9860
-------- -------- --------
INTERVAL 181.4350 198.3200
CPUADDR=1
INTERVAL USER CONECTTM CPUVIRT CPUTOTAL
19:30:28 SYSTEM 0 0.0000 9.3950
19:30:28 UNIPRD2 599 314.4460 398.7250
19:30:28 UNIPROD 599 266.6670 276.0360
19:30:28 UNITEST 599 0.5780 0.6260
-------- -------- --------
INTERVAL 581.6910 684.7820
CPUADDR=0
INTERVAL USER CONECTTM CPUVIRT CPUTOTAL
19:30:28 AUDITOR 599 0.1750 0.2220
19:30:28 DISKACNT 599 0.0150 0.0380
19:30:28 EREP 599 0.0000 0.0020
19:30:28 FAQSEXEC 599 0.0000 0.0000
19:30:28 FAQSVM 599 0.0030 0.0060
19:30:28 FTPIFOX 599 0.0000 0.0000
19:30:28 FTPSERVE 599 0.0000 0.0000
19:30:28 FWER 599 0.0000 0.0000
19:30:28 GCS 599 0.0000 0.0000
19:30:28 HIDRO 599 33.1660 41.8210
19:30:28 IFXSERVE 599 0.0000 0.0000
19:30:28 LINMON 599 0.0020 0.0040
19:30:28 OPERATOR 599 0.0070 0.0160
19:30:28 OPERSYMP 599 0.0000 0.0000
19:30:28 OSASF 599 0.0000 0.0000
19:30:28 PGAR 599 0.0000 0.0000
19:30:28 PHRO 599 0.0000 0.0000
19:30:28 RAHM 599 0.0000 0.0000
19:30:28 RMCG 599 0.0090 0.0320
19:30:28 RMSMASTR 599 0.0000 0.0000
19:30:28 RSCS 599 0.0000 0.0000
19:30:28 SESQ 599 0.0000 0.0000
19:30:28 SKAN 599 0.0000 0.0000
19:30:28 SK01 599 0.0050 0.0130
19:30:28 SPOOLER 599 0.0000 0.0010
19:30:28 SUBMITS 599 0.0020 0.0070
19:30:28 SYBCOM 599 0.0000 0.0000
19:30:28 SYBLOG 599 0.0000 0.0000
19:30:28 SYBMON 599 0.0000 0.0000
19:30:28 SYBUSER 599 0.0020 0.0030
19:30:28 SYSCHECK 599 0.0000 0.0000
19:30:28 SYSLOGS 599 0.0000 0.0000
19:30:28 SYSTEM 599 0.0000 11.0860
19:30:28 TCPIFOX 599 0.0380 0.0550
19:30:28 TCPIP 599 0.0070 0.0090
19:30:28 TMON 599 0.1720 0.1940
19:30:28 TS09 599 0.0740 0.0860
19:30:28 UACSERV 599 0.0000 0.0000
19:30:28 UAFCSERV 599 0.0000 0.0000
19:30:28 UNIJCL 599 0.0000 0.0000
19:30:28 UNIPRD2 599 316.9930 401.7960
19:30:28 UNIPROD 599 291.7980 302.0340
19:30:28 UNITEST 599 0.7500 0.8200
19:30:28 VGLIBSRV 599 0.0020 0.0020
19:30:28 VMLIB 599 0.0000 0.0000
19:30:28 VMSERVR 599 0.0000 0.0000
19:30:28 VMSERVS 599 0.0000 0.0000
19:30:28 VMSERVU 599 0.0000 0.0000
19:30:28 VMUTIL 599 0.0030 0.0050
19:30:28 VTAM 599 0.2320 0.3640
19:30:28 VTAMOP 599 0.0000 0.0000
19:30:28 WMOO 599 0.0000 0.0000
-------- -------- --------
INTERVAL 643.4550 758.6160
-----Original Message-----
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On
Behalf Of Barton Robinson
Sent: Friday, February 18, 2011 11:05 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VM Total time in $ACCOUNT files
and for linux servers with multiple cpus, you divide cputime by the
number of cpus?
Ackerman, Derek wrote:
> Yes, and I always divide the CPU time by 1000.
>
>
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU]
On Behalf Of Bruce Hayden
> Sent: Friday, February 18, 2011 10:14 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: VM Total time in $ACCOUNT files
>
> Hopefully you're converting the units. Virtual and Total time are in
> milliseconds and connect time is in seconds. Are you seeing this even
> after converting all of them to the same units?
>
> On Fri, Feb 18, 2011 at 1:04 PM, Ackerman, Derek
> <derek.acker...@infocrossing.com> wrote:
>> I always thought that the total VM time, as well as the virtual,
would
>> be less than the connect time. Is it normal for the total time to be
>> greater than the connect time? This happens a lot...
>>
>> Derek Ackerman
>> Enterprise Capacity Planning
>> & Performance Management
>> Infocrossing Inc
>>
>> Confidentiality Note: This e-mail, including any attachment to it,
may contain material that is confidential, proprietary, privileged
and/or "Protected Health Information," within the meaning of the
regulations under the Health Insurance Portability & Accountability Act
as amended. If it is not clear that you are the intended recipient, you
are hereby notified that you have received this transmittal in error,
and any review, dissemination, distribution or copying of this e-mail,
including any attachment to it, is strictly prohibited. If you have
received this e-mail in error, please immediately return it to the
sender and delete it from your system. Thank you.
>>
>
>
>
Confidentiality Note: This e-mail, including any attachment to it, may contain
material that is confidential, proprietary, privileged and/or "Protected Health
Information," within the meaning of the regulations under the Health Insurance
Portability & Accountability Act as amended. If it is not clear that you are
the intended recipient, you are hereby notified that you have received this
transmittal in error, and any review, dissemination, distribution or copying of
this e-mail, including any attachment to it, is strictly prohibited. If you
have received this e-mail in error, please immediately return it to the sender
and delete it from your system. Thank you.
