public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: [BENCHMARKS] 2.6.4 vs 2.6.4-mm1
Date: Sat, 13 Mar 2004 11:55:59 +1100	[thread overview]
Message-ID: <40525C1F.5030705@cyberone.com.au> (raw)

These are some benchmarks on a 16-way (4x4) NUMAQ. Basically
measures the scheduler patches with a couple of meaningless
but very scheduler intensive benchmarks.

hackbench:
The number in () is a projection for the time 1000 would take,
assuming a linear scaling. It is probably better shown on a
graph, but you can see a non linear element in 2.6.4 that is
basically absent in 2.6.4-mm1.

              2.6.4    2.6.4-mm1
 50      19.4 (388)   15.5 (310)
100      39.0 (390)   34.5 (345)
150      59.0 (393)   48.3 (322)
200      82.9 (414)   68.9 (344)
250     114.8 (459)   90.2 (360)
300     145.4 (484)  106.3 (354)
350     178.1 (508)  122.1 (348)
400     218.8 (547)  135.0 (337)
450     237.8 (528)  163.9 (364)
500     262.0 (524)  181.7 (363)

volanomark (MPS):
This one starts getting huge mmap_sem contention at 150+ coming
from futexes. Don't know what is taking the mmap_sem for writing.
Maybe just brk or mmap.

        2.6.4   2.6.4-mm1
 15      5850        6221
 30      5682        5852
 45      4736        5700
 60      2857        5622
 75      1024        4840
 90      1832        5191
105       491        5036
120      1591        4228
135       393        4986
150      1056        1586


             reply	other threads:[~2004-03-13  0:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-13  0:55 Nick Piggin [this message]
2004-03-19  9:50 ` [BENCHMARKS] 2.6.4 vs 2.6.4-mm1 Ingo Molnar
2004-03-19  9:58   ` Nick Piggin
2004-03-21  4:04     ` Nick Piggin
2004-03-21  7:31       ` Ingo Molnar
2004-03-21  8:08         ` Nick Piggin

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=40525C1F.5030705@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.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