All
I should have put more thought into this rather than just copying some
text with the formula.
John made me realize that I should have added my personal thoughts about
this. Personally, I know of no one with the patience to calculate an
alias value for each and every LCU in their shop.
You are moving to a new box, so you need to look at your current peak I/O load,
for each LPAR and calculate (on an LCU basis) how loaded your new LCUs will be.
The method shown below is a good starting point, but pick your factor to cope
with bursts of I/O activity. Since HyperPAVs are assigned
2 * [ (SSCH Rate) * (Average I/O Service Time) ] = # of Proposed Aliases
Example -- assumptions are 2000 SSCH for the LCU with an average I/O
service time of 5 milliseconds.
2 * [ (2000) * (.005) ] = 2 * 10 = 20 Aliases for the LCU
Note ... Make this calculation at the LCU level as the alias
Hello,
We are installing a new DASD array with 33 TB of capacity with
approximately 1/3 of the capacity being setup as 3390-3's, 1/3 as 3390-9's
and the last 1/3 as 3390-27's. I am wondering if anyone has any experience
or documentation that would suggest how many Hyper PAVs per LCU we should
def
4 matches
Mail list logo
