linux-ext4 - Re: jbd/jbd2 performance improvements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <18688.27755.969223.822862@frecb006361.adech.frec.bull.fr>
Date:	Thu, 23 Oct 2008 14:22:03 +0200
From:	Solofo.Ramangalahy@...l.net
To:	Arjan De Ven <arjan.van.de.ven@...el.com>
Cc:	Eric Sandeen <sandeen@...hat.com>,
	Ric Wheeler <rwheeler@...hat.com>,
	"Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: jbd/jbd2 performance improvements

Ric Wheeler writes:
 > Do you have any details on the test case that you ran that showed a 
 > clear improvement? What kind of storage & IO pattern did you use?

Is it possible to record latencytop output (like top batch mode) to
capture the highest latency during a test run?

Or how did you collect this:
>my reproducer is sadly very simple (claws-mail is my mail client that uses maildir)
>Process claws-mail (4896)                  Total: 2829.7 msec
>EXT3: Waiting for journal access                  2491.0 msec         88.4 %
>Writing back inodes                                160.9 msec          5.7 %
>synchronous write                                   78.8 msec          3.0 %
>is an example of such a trace (this is with patch, without patch the numbers are about 3x bigger)
>Waiting for journal access is "journal_get_write_access"
>Writing back inodes is "writeback_inodes"
>synchronous write is "do_sync_write"


-- 
solofo


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html