Re: Transaction logging.

You don't need to do anything different as long as your disk drives aren't
already experiencing usage/utilization problems. IIRC, Walter said you'll
see about a 3% hit by starting transaction logging, but you'll probably
recoup that once you setup DAOS and see the reduced I/O overhead that it
will likely bring.

---------------------------------------------------

Thanks,
Chris
Personal Blog: http://cwhisonant.blogspot.com
Work Blog: http://www.bleedyellow.com/blogs/lotusnut


On Mon, Jun 1, 2009 at 2:17 PM, <rob@xxxxxxxxx> wrote:

Went to an IBM & Partner intro to 8.5 last week. One of the new options
we may look at requires transaction logging be fired up. Most of the time
when I hear about transaction logging it makes me think of something
primarily run in a lab or on a test machine. Because, they mention
keeping your data on one drive and your transaction logs on another drive.
Well, my machine has ninety disk drives. All Raid 5 protected. Does it
really make sense to put the transaction log on dedicated disk? On the i
that would involve Auxiliary Storage Pools or ASPs. In theory I could
have two ASPs: Main data in one and transaction logging in the other. I
can't imagine it would take more than a few 70gb disks to do transaction
logging.
Raid sets smaller than 4 drives are known to have serious performance
implications. Technically you can do a 3 drive raid set, but unless the
customer is just migrating from a S/36 they will notice the performance
hit versus a 4 drive (or more) set.

Is this separate disk stuff recommended on a "real" os?
Do I need a full RAID set in an ASP?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

_______________________________________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.