Re: TBLSPACE table extents. -Reply

In article <4qbopp$nqe@news.informix.com>, June Tong <junet@informix.com> writes >Paul Daniels (paul.daniells@lovellwhitedurrant.com) wrote: >: Jack's suggestion works fine on database tables, unfortunately I did not >: make myself clear, the TBLSPACE TBLSPACE I was referring to is the >: internal one which holds information on table location within a dbspace, >: and shows up best when using "oncheck -pe". > >: This has become badly extended on all three of our systems which run >: different applications. This did not happen on version 5. > >: Any further ideas ? or maybe I should not worry about it ? > >You should not worry about it. First of all, there really isn't anything you >can do about it. Secondly, it doesn't really matter. People are always >worrying about having too many extents on a table (I think the importance of >keeping under 9 extents is highly overrated myself -- it's one extra disk read >IF the extra page isn't already in shared memory -- but that's just a personal >opinion). For the tblspace tblspace, it matters even less, since the tblspace >page of any table you use regularly will almost always be in shared memory. > That what I thought, one extra disk read, but the person who gave me my OnLine Performance Tuning course talked with a programmer in Menlo Park who checked the code and he said that it did make a bigger difference that just one extra disk read.... Could you check with the coding team for us, please...please...go on. -- David Williams