What type of hardware setups are you using, single core or ?? Do you have
any performance data based on what you want to create.

On Wed, Jun 22, 2011 at 3:43 PM, Evan Harris <auctionitis@xxxxxxxxx> wrote:

Hi Jim

Thanks for the response.

Part of the reasoning for separating the IO was due to performance
issues seen on other guests; we were looking at a minimum of 4 drives
for the application servers, not just one or two (not sure if I had
made that clear).

Following on from your response, is there any rule of thumb as to how
many to create, or what sizes to make the storage spaces ?

Making one large storage space will create I/O problems of it's own if
what my IBM resource has told me is accurate.

Do you have any best practise guidelines for this aspect ?

On Wed, Jun 22, 2011 at 11:37 PM, Jim Oberholtzer <midrangel@xxxxxxxxxx>

Based on your description of the situation, I think most will agree that
best practice would have you create your storage spaces in SYSBAS. If
you isolate the drives for the storage spaces you will degrade the I/O
capacity to a point where I wonder if the performance of the guest
partitions would be sufficient. Allow IBM i to do what it does best,
manage storage.

If you had an iASP that had many disk units in it to eliminate the I/O
issues, then you could consider that. For now I would create the
storage spaces as needed and let them do their thing.

Evan Harris
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].