Re: Best practices for IDS on virtual machine?

Sorry, Colin, I missed your question at the end. Best not to bottom post! Yes, in part recommeding EXT2 is to avoid journaling overhead. The rest is the copy-on-write feature which physically fragments your chunks over time. As to the others, see my presentation from last year's IIUG Conference, "Doing Storage Better" which includes a table of timings I ran (available in the members' pages on the IIUG web site - www.iiug.org). Also see a post to the forums that Eric did last month where he posted his own timings which agree. Yes, Informix logging eliminates the need for FS journaling. It's covered with over 20 years of experience proving that it works, why duplicate it with an inferior version? Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Sat, Apr 13, 2013 at 4:45 AM, colin mcdermott < colinjamesmcdermott@gmail.com> wrote: > > - IBM's Hypervisor has the lowest overhead and highest IO rates. > - If you must use VMWare make sure you are using the vSphere > hypervisor, it's IO is about double the older hypervisors from VMWare or > running without one. > - Yes RAID10. > - As much as possible make sure you do not have competition for the > physical disks underneath your LUNS, ESPECIALLY not Windows Filesystems and > NEVER email stores. The access patterns are just too different from > database access patterns. > - EXT2 with DIRECT_IO, yes. > - Yes to separate dbspaces for high access data like rootdb, logical > logs, physical logs, high access tables and indexes. Informix assigns IO > resources per dbspace and per chunk depending on specifics. More dbspaces > and more chunks can lead to more total IO throughput. Keeping logical logs > on different LUNs from physical logs and from high IO data dbspaces will > take advantage of more physical resources like IO channels and spindles. > > Apologies for the previous mispost, Moderators please delete. > > I notice that you recommend ext2 with DIRECT_IO. Is this to avoid the > journaling overhead of ext3? Is there a substantial performance boost in > switching to ext2? Is JFS or Reiserfs better for this. I take it that the > Plog and Llog should remove the need for the journal in ext3. > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > >