Steven Cole wrote:
>
> I found that dbench gives significantly lower numbers when
> the partition on which it is run is mounted as ext3.
>
ext2 will force writeback when 40% of ZONE_NORMAL is dirty.
That's normally >300 megabytes.
ext3 will force writeback when 75% of the journal space is
consumed by metadata. That's normally 24 megabytes.
dbench generates a storm of metadata and data and then deletes it all.
It consumes the journal space almost immediately and forces ext3
to do a lot of writeback. ext2 benefits because most of the metadata
and data are deleted before they ever touch disk.
If your application generates unusually high volumes of metadata
and data and then immediately deletes it, ext3 may not be an
appropriate filesystem.
-
-
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/
This archive was generated by hypermail 2b29 : Tue Jul 30 2002 - 14:00:24 EST