From: Diego Calleja <diegocg@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Performance regressions in 2.6.30-rc7?
Date: Sat, 30 May 2009 18:51:47 +0200 [thread overview]
Message-ID: <200905301851.47708.diegocg@gmail.com> (raw)
In-Reply-To: <20090529210718.bef7a9c1.akpm@linux-foundation.org>
On Sábado 30 Mayo 2009 06:07:18 Andrew Morton escribió:
> Those regressions are huge. They appear to be on compute-intensive
> workloads too.
>
> I wonder if some expensive debugging option turned itself on or
> something silly like that.
They use the vanilla kernels that ubuntu ship with their own configs,
so they shouldn't be using any expensive debugging option.
I've run myself two of those tests (I've not tested gnupg as I'm
allergic to it). I can't reproduce any regression with 7zip, I'm however
able to reproduce the regression in tiobench write latency, using 32
threads and 64 MB block size (--threads 32 --block 65536). I used ext4
(phoronix uses ext3).
Random Writes
File Blk Num Avg Maximum Lat% Lat% CPU
Identifier Size Size Thr Rate (CPU%) Latency Latency >2s >10s Eff
---------------------------- ------ ----- --- ------ ------ --------- ----------- -------- -------- -----
2.6.29 2000 65536 32 24.16 107.2% 0.051 0.21 0.00000 0.00000 23
Random Writes
File Blk Num Avg Maximum Lat% Lat% CPU
Identifier Size Size Thr Rate (CPU%) Latency Latency >2s >10s Eff
---------------------------- ------ ----- --- ------ ------ --------- ----------- -------- -------- -----
2.6.30-rc7-00149-g3218911 2000 65536 32 23.06 178.4% 0.711 164.72 0.00000 0.00000 13
next prev parent reply other threads:[~2009-05-30 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 20:49 Performance regressions in 2.6.30-rc7? Diego Calleja
2009-05-30 4:07 ` Andrew Morton
2009-05-30 16:51 ` Diego Calleja [this message]
2009-06-03 19:58 ` Jan Kara
[not found] ` <1244100382.7131.12.camel@marge.simson.net>
[not found] ` <20090604112109.GC2859@duck.suse.cz>
[not found] ` <1244142795.5731.31.camel@marge.simson.net>
2009-06-09 10:32 ` Jan Kara
2009-06-09 18:48 ` Chris Mason
2009-06-10 9:12 ` Jan Kara
2009-06-10 22:12 ` Jeff Moyer
2009-07-15 10:43 ` Jan Kara
2009-07-15 13:41 ` Jeff Moyer
2009-07-15 14:58 ` Jan Kara
2009-07-15 17:50 ` Jan Kara
2009-07-15 18:54 ` Jan Kara
2009-07-16 14:36 ` Jeff Moyer
2009-07-16 14:46 ` Jan Kara
2009-07-16 14:59 ` Jeff Moyer
2009-07-16 16:34 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905301851.47708.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox