I''ve seen this question asked in a number of forums but I haven''t seen an answer. (May just have not looked hard enough) Copy-on-write means that most writes are sequential, which is good for write performance, but won''t it mean that random writes to a file will put bits of the file all over the place? How does this affect sequential read performance? Does ZFS'' read- ahead mean that this isn''t the problem it could be? Boyd Melbourne, Australia
> I''ve seen this question asked in a number of forums but I haven''t > seen an answer. (May just have not looked hard enough) > > Copy-on-write means that most writes are sequential, which is good > for write performance, but won''t it mean that random writes to a file > will put bits of the file all over the place? > > How does this affect sequential read performance? Does ZFS'' read- > ahead mean that this isn''t the problem it could be?That was discussed to some extent in this thread: http://www.opensolaris.org/jive/thread.jspa?messageID=14997 -- Darren Dunham ddunham at taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
On 11/05/2006, at 9:04 AM, Darren Dunham wrote:>> I''ve seen this question asked in a number of forums but I haven''t >> seen an answer. (May just have not looked hard enough) >> >> Copy-on-write means that most writes are sequential, which is good >> for write performance, but won''t it mean that random writes to a file >> will put bits of the file all over the place? >> >> How does this affect sequential read performance? Does ZFS'' read- >> ahead mean that this isn''t the problem it could be? > > That was discussed to some extent in this thread: > http://www.opensolaris.org/jive/thread.jspa?messageID=14997Thanks, exactly what I was after. Boyd Melbourne, Australia