Largest chunk size < largest extent size?!? (fwd)

> From: aburt@mnemosyne.cs.du.edu (Andrew Burt) > Subject: Largest chunk size < largest extent size?!? > Date: Fri, 9 Apr 93 13:40:32 GMT > > . . . . > > Now following the advice of the online admin manual, which says "make your > chunks large" (since you can have only a small number of them), I set up > the raid array to be one logical disk as 4Gb (it's 5 x 1.2Gb disks, with > 1/5 of it used for parity information). > > (lots -o- questions deleted) > Hey folks, can we possibly expand this into a more general "Gosh, I've got 4 Gig of data to manage, where do I start!". We have a system that we're designing that will be hitting at LEAST 4 Gig in a few months. Things start taking a LONG time when the system gets that big, plus we're pushing the limits of archive mediums. I also remember hearing horror stories about reindexing million row tables etc. So, just some general ideas about managing LARGE volumes of data would be appreciated. This system may use OnLine 5.0, preferably 5.01 if it's out when we are ready, otherwise we'll just stick with 4.1. Thanx! Will (uunet!la4gen!villy -or- me@zipbang.socal.com)