Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: LMT and Siebel/Peoplesoft?
Don't use one tablespace size. Create three or four for data and three or four for indexes. For example
data_sml 256K data_med 2.5M data_lrg 25M data_ext 250M
Or whatever works for you.
Daniel Morgan
Vikas Agnihotri wrote:
> "Daniel A. Morgan" <damorgan_at_exesolutions.com> wrote in message news:<3C4A963E.72AB93F5_at_exesolutions.com>...
> > They make sense only if you value performance and dislike fragmented
> > tablespaces. Otherwise just ignore them.
>
> Um. Maybe you didnt read my post entirely. I know that LMTs offer
> performance benefit and eliminate fragmented tablespaces.
>
> But in the context of apps like Siebel and Peoplesoft, where objects
> range from 100K to 50-100M, what is a good extent size to use for a
> LMT with uniform extent allocation policy? Note that 80% of the
> objects are in the 100k ballpark.
>
> If I use a extent size of, say, 256K or even 1M, I waste a lot of
> space since most objects are 100K. If I use a extent size of 100K, the
> larger objects end up having 100s of extents (which is bad, right?)
>
> Thanks
Received on Sun Jan 20 2002 - 15:28:46 CST