Heya Roch, On 10/17/06, Roch <[EMAIL PROTECTED]> wrote: -snip-
Oracle will typically create it's files with 128K writes not recordsize ones.
Darn, that makes things difficult doesn't it? :( Come to think of it, maybe we're approaching things from the wrong perspective. Databases such as Oracle have their own cache *anyway*. The reason why we set recordsize is to 1) Match the block size to the write/read access size, so we don't read/buffer too much. But if we improved our caching to not cache blocks being accessed by a database, wouldn't that solve the problem also? (I'm not precisely sure where and how much performance we win from setting an optimal recordsize) Thanks for listening folks! :) -- Regards, Jeremy _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
