linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* commit only journal entries older than commit period?
@ 2007-05-09 13:31 Leon Woestenberg
  2007-05-09 16:20 ` Andreas Dilger
  0 siblings, 1 reply; 2+ messages in thread
From: Leon Woestenberg @ 2007-05-09 13:31 UTC (permalink / raw)
  To: linux-ext4

Hello all,

this is something I have long wondered about but have been afraid to ask.

When my system is chewing away on builds, the disk I/O write access
pattern of my ext3 root filesystem (using CFQ, Intel SATA controller,
hard disk) when visualized by GNOME System Monitor clearly shows a
repetitive landscape of large peaks, 5 seconds apart, which not much
activity inbetween.

I understand that's due to the ex3 journal commit interval (defaults
to 5 seconds).

But why isn't the filesystem continuously committing only that part of
the journal that is older than 5 seconds?

I would then expect the write requests to be smoothened over time,
which can only be good in terms of performance and low latency.

Regards,
-- 
Leon

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: commit only journal entries older than commit period?
  2007-05-09 13:31 commit only journal entries older than commit period? Leon Woestenberg
@ 2007-05-09 16:20 ` Andreas Dilger
  0 siblings, 0 replies; 2+ messages in thread
From: Andreas Dilger @ 2007-05-09 16:20 UTC (permalink / raw)
  To: Leon Woestenberg; +Cc: linux-ext4

On May 09, 2007  15:31 +0200, Leon Woestenberg wrote:
> this is something I have long wondered about but have been afraid to ask.
> 
> When my system is chewing away on builds, the disk I/O write access
> pattern of my ext3 root filesystem (using CFQ, Intel SATA controller,
> hard disk) when visualized by GNOME System Monitor clearly shows a
> repetitive landscape of large peaks, 5 seconds apart, which not much
> activity inbetween.
> 
> I understand that's due to the ex3 journal commit interval (defaults
> to 5 seconds).
> 
> But why isn't the filesystem continuously committing only that part of
> the journal that is older than 5 seconds?
> 
> I would then expect the write requests to be smoothened over time,
> which can only be good in terms of performance and low latency.

The journal cannot start checkpoint of blocks to the filesystem until
the transaction is committed, otherwise a crash would leave the filesystem
inconsistent.  After the transaction is committed the blocks are written
into the fs and I'd guess that this can happen quickly enough that it
only takes a fraction of a second.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-05-09 16:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-09 13:31 commit only journal entries older than commit period? Leon Woestenberg
2007-05-09 16:20 ` Andreas Dilger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).