public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: ck list <ck@vds.kolivas.org>
Subject: [ANNOUNCE] Interbench v0.24
Date: Fri, 29 Jul 2005 13:10:39 +1000	[thread overview]
Message-ID: <200507291310.42203.kernel@kolivas.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]

Interbench is a Linux Kernel Interactivity Benchmark.

Direct download:
http://ck.kolivas.org/apps/interbench/interbench-0.24.tar.bz2
Web:
http://interbench.kolivas.org

Changes:
3 new loads were added:

Gaming benchmark:
This simulates an unlocked frame rate cpu intensive 3d gaming environment. It 
measures the latencies mean/sd/max and desired cpu percentage only. These 
should give a marker of frame rate stability (latencies), and maximum frame 
rates under different loads (desired cpu percentage). As this simulates an 
unlocked frame rate the deadlines met is meaningless. This does not 
accurately emulate a 3d game which is gpu bound, only a cpu bound one.

Hackbench:
Taken from Rusty's hackbench code as suggested by Ingo Molnar, this will run 
'hackbench 50' repeatedly in the background when benchmarking real time 
performance.

Custom:
Based on the periodic scheduling used for audio/video, custom will allow you 
to specify a cpu percentage and frame rate of a custom workload, and this can 
be used to benchmark this workload's performance under normal scheduling, 
real time scheduling or it can be used as a background load.


Bugfixes:
Numerous floating point and overflow errors were tracked down and fixed. These 
are responsible for results like 'nan' and 4294... which is basically 2^32. 
Unfortunately the standard deviation reported in previous versions appears to 
have been bogus, but fortunately little value was placed on this result.

Error handling was made _much_ more robust - for example it was found that 
contrary to 'man sem_wait' but consistent with SUSv3, sem_wait can return -1 
with -EINTR.

Lots of little tweaks.


Cheers,
Con

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-07-29  3:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29  3:10 Con Kolivas [this message]
     [not found] ` <42EA0EF8.2040202@staticwave.ca>
2005-07-29 11:27   ` [ck] [ANNOUNCE] Interbench v0.24 Con Kolivas
2005-07-29 11:47     ` Gabriel Devenyi
2005-07-29 11:49       ` Con Kolivas
2005-08-02  7:08 ` Peter Williams
2005-08-02  7:13   ` Con Kolivas

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=200507291310.42203.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ck@vds.kolivas.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