Re: large disks

I need to emphasize that I have not tested this idea and have no idea if it is a good idea or not. At this point, it is just a thought. I haven't tested it at all. M.P. "Madison Pruet" <mpruet@comcast.net> wrote in message news:4tVUb.241751$na.398369@attbi_s04... > Well ---- > > Since you are going to be moving to 9.4, you could just put the whole thing > into a single chunk.... ;-) (Guess you can't tell that I worked on that a > while back...);-) > > While I'm being a bit silly, there is some truth to saying this. We've > tried through the years to use all kinds of algorithms to schedule IO. > However, with more recent disk technology, this type of logic a bit > unnecessary. So by putting more in a single larger chunk might actually > lessen the impact of the software IO scheduling by chunk. But that might be > offset by the hardware IO scheduling. > > M.P. > "Campbell, John (GE Consumer Finance)" <John.Campbell2@ge.com> wrote in > message news:c013es$akm$1@terabinaries.xmission.com... > > > > Solaris 2.8, IDS 9.30.UC6W1, Enterprise 6000. We have a new SunFire 6800 > and are in the process of ordering 2 3510 storage arrays. We plan to be on > 64 bit 9.4x, Solaris 9 before moving to the new server. What is the best way > to lay out these large disks - stipe and mirror? Currently, we have a ton > of old 2 gig disks with a few 18 and 32s thrown in. We don't have the > current disks striped but do have access to Veritas. We are not using nor > plan to use RAID5 and will probably go with hardware mirroring. I have the > opportunity to start with fresh hardware and would greatly value any > suggestions or lessons learned. > > > > sending to informix-list > >