Re: data file sizes

Extent size and number of extents (within reason < 1000) has nothing to do with performance except in the case of truncating or droping (can be quite significant in these cases) an object (table, index etc). All the extent performance stuff is old Oracle mythology.

I generally would go for more files of less size say 2G. Oracle typically does its TPC-D benchmarks with 2G files. Much easier to deal with from a management point of view, not to mention keeping away from the thin ice of 2G boundaries where both Oracle amd most platforms have or have had nasty bugs.

Best
Kyle

In article <93nujg$5q8$1_at_nnrp1.deja.com>,   Joe Maloney <jrpm_at_my-deja.com> wrote:
> The performance implications are related to extent size and platform.
>
> Smaller files give better performance on Unix (smaller inodes).
> Smaller extents give better OLTP performance, larger extents better
> OLAP performance.
>
> Nutshell: Depends on your app and platform.
>
> In article <93nehn$mbc$1_at_nnrp1.deja.com>,
> gdas_at_my-deja.com wrote:
> > Hi,
> >
> > Are there any performance considerations to take into account when
> > sizing index and data tablespace datafiles? Do fewer but larger
> > datafiles have any performance benefits to More but smaller
 datafiles?
> > Does the fact that the files are on RAID 5 change the answer.
> >
> > I've seen some posts here that support more but smaller files due to
> > increased manageability, but I was curious if there were any
> > performance implications.
> >
> > Thanks,
> > Gavin
> >
> > Sent via Deja.com
> > http://www.deja.com/
> >
>
> --
> Joseph R.P. Maloney, CCP,CSP,CDP
> MPiR, Inc.
> 502-451-7404
> some witty phrase goes here, I think.
>
> Sent via Deja.com
> http://www.deja.com/
>

Sent via Deja.com
http://www.deja.com/ Received on Fri Jan 12 2001 - 17:52:35 CST