I found Larry's notes from Feb 2013.
Any update or revisions with P8.
"At iDevCloud.com we have standardized on 17GB disks for our private partition users. You need 17GB for the load source and by the time you load up all the LPPs (we have a very heavy load of LPPs) you use up about 2 1/2 17's. Then add a few more and you've got enough space for the user.
So from a practical standpoint that's about as small as you can even go and stick with the 6 drive minimum. And remember that more than 6 arms is better for performance and more than one vSCSI path between host and client is also better for performance.
Essentially you need to work out how much I/O capacity you need and how much storage capacity you need and then work the two together to come up with the correct number and size of arms."
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Wednesday, December 09, 2015 7:45 PM
To: 'Midrange Systems Technical Discussion'
Subject: Concepts and guidelines for client virtual disks, i hosting i
I'm looking for the latest Concepts and guidelines for client virtual disks, I hosting i These will be for limited usage sand box LPAR and a base LPAR to create DSLO combined OS/PTF upgrade images.
I remember a discussion/thread related to this, was not able to locate in the archives.
I reviewed many PDF, Redbooks, links, (most were dated) not finding answers to below.
What size should each NWS be created as? minimum of 17GB (Gigabyte) and maximum size of 1TB (Terabyte).
How many NWS should be created?
Should NWS be kept equal in size?
How many vSCSI adapters should be created?
How many NWS should be linked to each vSCSI adapter? limited to 16 virtual drives per SCSI adapter
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l