Hi Tom,
thanks for reply.
yes, I know the weight value is absolutely different thing to MIPS...
But fact is, we do use the *number* as "Initial Processing Weight". The
calculation is: we need 24 MSU out of 26, the rate is about 93%. And in
terms of MIPS,
our 26 MSU is about 170 MIPS. So, we put the weight to SYS2 as 160. (
170*93%), and the dummy LP weight 10.

On Thu, Nov 4, 2010 at 2:15 AM, Kelman, Tom
<[email protected]>wrote:

> Cobe,
>
> You do have me a little confused when you talk about capping at 24 MSUs
> and setting the WEIGHT (which I assume is the LPAR weighting factor) to
> 160.  These are different.  Also, the LPAR weighting factor is just a
> relative number.  It does not relate to MIPS.
>
> As far as the LPAR going over the cap in any given interval, that can
> occur as long as the MSU four hour rolling average (4HRA) remains below
> the cap.  It is when the 4HRA hits the cap that you'll see the peaks
> chopped off.  Once the 4HRA falls below the cap the system can once
> again spike up above that.  If you have a cap set, and you are on
> sub-capacity pricing, IBM's software charges for the sub-capacity priced
> software will be based on the highest 4HRA for the month, but will never
> exceed the cap.  Actually, if you are not using sub-capacity pricing for
> your software, I can't think of any reason to set a cap.
>
> Tom Kelman
> Capacity Planning
> Commerce Bank, Kansas City
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Cobe Xu
> Sent: Wednesday, November 03, 2010 5:00 AM
> To: [email protected]
> Subject: CPU capping is not working for one Lpar only on CEC?
>
> Hi list,
> We aim to cap the only active LPAR on the CEC(26 MSU) to 24 MSU.
> But, I'm a bit confuse when I checked the RMF CPU Activity report as
> below,
> which shows that with the interval, SYS2 was able to use up to 25 MSU.
> (Highlighted)
> So my questions are:
> 1. Is this because CPU capping is not working for only one active LPAR
> on
> the CEC? If it's the case, any reference?
> 2. Or, this is related to the WEIGHT value we used to CAP? in our case,
> we
> reference our CEC capacity is 26 MSU (about 171 MIPS), target to CAP 24
> MSU
> (160 MIPS).
> . But, for client's sake, we use MIPS value as the WEIGHT,i.e 160. (as
> highlighted in the report). And, this mislead the Lpar scheduler that it
> is
> over 100% of the CEC. Thus,
>  SYS2 can use as much as it needs.
> 3. Or any other posibility?
> Pls shed some light, thanks a lot!
>
>
>
> PAGE    2
>            z/OS V1R8                SYSTEM ID SYS2             START
> 08/17/2010-03.00.00  INTERVAL 000.59.59
>                                     RPT VERSION V1R8 RMF       END
> 08/17/2010-04.00.00  CYCLE 0.100 SECONDS
>
>
> MVS PARTITION NAME                    SYS2        NUMBER OF PHYSICAL
> PROCESSORS           4                 GROUP NAME       N/A
> IMAGE CAPACITY                          24
> CP                            2                 LIMIT            N/A
> NUMBER OF CONFIGURED PARTITIONS          5
> ICF                           2
> WAIT COMPLETION
> NO
>
> DISPATCH INTERVAL
> DYNAMIC
>
> --------- PARTITION DATA -----------------  -- LOGICAL PARTITION
> PROCESSOR
> DATA --   -- AVERAGE PROCESSOR UTILIZATION PERCENTAGES --
>                   ----MSU----  -CAPPING--  PROCESSOR-  ----DISPATCH
> TIME
> DATA----   LOGICAL PROCESSORS  --- PHYSICAL PROCESSORS ---
> NAME       S   WGT  DEF    ACT  DEF   WLM%  NUM   TYPE   EFFECTIVE
> TOTAL       EFFECTIVE    TOTAL  LPAR MGMT  EFFECTIVE  TOTAL
> SYS2       A   160    0     25  YES    0.0    2   CP    01.55.49.238
> 01.55.53.278       96.52    96.57      0.06      96.52  96.57
> SYS6       A    10    0      0  YES    0.0    2   CP    00.00.00.000
> 00.00.00.000        0.00     0.00      0.00       0.00   0.00
> *PHYSICAL*
> 00.00.01.367                           0.02              0.02
>                                                        ------------
> ------------                         ------     ------ ------
>  TOTAL                                                 01.55.49.238
> 01.55.54.645                           0.08      96.52  96.59
>
>
> CFP01AH2   A   DED                            1   ICF   00.59.59.655
> 00.59.59.725       99.99    99.99      0.00      50.00  50.00
> CFP02AH2   A   DED                            1   ICF   00.59.59.666
> 00.59.59.708       99.99    99.99      0.00      50.00  50.00
> *PHYSICAL*
> 00.00.00.422                           0.01              0.01
>                                                        ------------
> ------------                         ------     ------ ------
>  TOTAL                                                 01.59.59.321
> 01.59.59.855                           0.01      99.99  100.0
>
>
> SYS8
> --
> Cobe Xu
>
> Best Regards
> -----------------------------------------------------------
> zOS Performance & Capacity Analyst
> E2E Performance Analyst
> Email: [email protected]
> -----------------------------------------------------------
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
>
>
> *****************************************************************************
> If you wish to communicate securely with Commerce Bank and its
> affiliates, you must log into your account under Online Services at
> http://www.commercebank.com or use the Commerce Bank Secure
> Email Message Center at https://securemail.commercebank.com
>
> NOTICE: This electronic mail message and any attached files are
> confidential. The information is exclusively for the use of the
> individual or entity intended as the recipient. If you are not
> the intended recipient, any use, copying, printing, reviewing,
> retention, disclosure, distribution or forwarding of the message
> or any attached file is not authorized and is strictly prohibited.
> If you have received this electronic mail message in error, please
> advise the sender by reply electronic mail immediately and
> permanently delete the original transmission, any attachments
> and any copies of this message from your computer system.
>
> *****************************************************************************
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>



-- 
Cobe Xu

Best Regards
-----------------------------------------------------------
zOS Performance & Capacity Analyst
E2E Performance Analyst
Email: [email protected]
-----------------------------------------------------------

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to