Messages in this thread | | | Date | Sat, 7 Aug 2004 18:54:58 -0700 | From | Thomas Zimmerman <> | Subject | Re: EXT intent logging |
| |
On 06-Aug 03:56, Theodore Ts'o wrote: > "mount -o data=journal" logs metadata blocks and data blocks into > journal first, and then after the transaction commits, the metadata > and data blocks are written to their final location on disk. The > problem with this is that all your write bandwidth is cut in half > since all block writes get written twice to disk --- once to the > journal, and once to the final location on disk.
While you do half your write bandwidth, there arn't any _seeks_ while writing to the journal. For IO workloads where a sync allows you to move on to another job, this can speed up your workload. Mail delivery on an old laptop disk was ~2 as fast using ext3 data=journal...
Thomas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |