Re: Question on Extent Size

I still keep to the 8 extents rule when calculating database sizing unless there is a good reason not to. I have observed that the system can take an appreciable time to add or even extend an extent and if that happens too frequently it is noticeable. regards Malcolm ----- Original Message ----- From: "Mark D. Stock" <mdstock@mydassolutions.com> To: "Abraham Kirubakaran" <bull_informix@yahoo.com> Cc: "KalpanaPai" <kalpanapai@hotmail.com>; <informix-list@iiug.org> Sent: Tuesday, September 16, 2003 9:39 PM Subject: Re: Question on Extent Size > Abraham Kirubakaran wrote: > > > As a general rule, make sure you don't exceed more > > than 8extents per fragment for a table, this helps > > performance. > > The 8 extents general rule applies to OnLine up to and including version 5. > From version 6, all extents are cached, so there is no real drop in > performance in terms of tracking extents after 8 extents. However, 1 extent > per fragment is best. If you get any were near 200 then you run the risk of > running out and getting errors. Any where in between and it depends on the > type of user access as to the affect on performance. > > Cheers, > -- > Mark. > > +----------------------------------------------------------+-----------+ > | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /| > | Mydas Solutions Ltd http://MydasSolutions.com |///// / //| > | +-----------------------------------+//// / ///| > | |We value your comments, which have |/// / ////| > | |been recorded and automatically |// / /////| > | |emailed back to us for our records.|/ ////////| > +----------------------+-----------------------------------+-----------+ > > sending to informix-list sending to informix-list