On Thu, 2006-05-11 at 10:31 -0600, Gregory Shaw wrote: > A couple of points/additions with regard to oracle in particular: > > When talking about large database installations, copy-on-write may > or may not apply. The files are never completely rewritten, only > changed internally via mmap(). When you lay down your database, you > will generally allocate the storage for the anticipated capacity > required. That will result in sparse files in the actual filesystems.
This is counter to my Oracle experience, which I'll admit is dated. Oracle will zero-fill the tablespace with 128kByte iops -- it is not sparse. I've got a scar. Has this changed in the past few years? Now, if compression is enabled, then this represents and interesting challenge... -- richard _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
