public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Devenyi <ace@staticwave.ca>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck@vds.kolivas.org, linux-kernel@vger.kernel.org,
	Jake Moilanen <moilanen@austin.ibm.com>
Subject: Re: [ck] [ANNOUNCE] Interbench 0.27
Date: Thu, 04 Aug 2005 07:44:09 -0400	[thread overview]
Message-ID: <42F1FF89.5030903@staticwave.ca> (raw)
In-Reply-To: <200508041004.46675.kernel@kolivas.org>

Hi Con,

You must hate me by now...

The "Gaming" benchmark has the same issue with nan coming out of the 
STDEV calculations, probably requires the same fix as before.

Secondly, the benchmarking of loops_per_ms is running forever, and I 
managed to determine where its happening.

In calibrate loops you run a while loop and iterate to get 1000 for 
run_time, then you calculate it one more time to ensure it was right 
*however* you put a sleep(1) before that. It seems to seriously skew the 
results, as it consistently adds ~500 to run_time, as run_time is now 
1500, it jumps back up to redo because of the goto statement, and runs 
the while loop again, continue ad nausium. I added some simple debugging 
output which prints run time at the end of each while loop, and right 
before the goto if statement, this is the output.

--cut--
loops_per_ms unknown; benchmarking...
while: 224
while: 649
while: 993
while: 1025
while: 976
while: 1001
while: 1000
1494
while: 671
while: 997
while: 1000
1496
--cut--

The solution I used is of course to simply comment out the sleep 
statement, then everything works nicely, however your comments appear to 
indicate that the sleep is there to make the system settle a little, 
perhaps another method needs to be used. Thanks for your time!

--
Gabriel Devenyi
ace@staticwave.ca

Con Kolivas wrote:
> Interbench is a benchmark application is designed to benchmark interactivity 
> in Linux.
> 
> Direct download link:
> http://ck.kolivas.org/apps/interbench/interbench-0.27.tar.bz2
> 
> Web page:
> http://interbench.kolivas.org
> 
> Changes:
> Standard deviation and average latency calculation was corrected. Gaming 
> standard deviation was implemented.
> 
> Cheers,
> Con
> _______________________________________________
> ck@vds.kolivas.org
> ck mailing list. Please reply-to-all when posting.
> If replying to an email please reply below the original message.
> http://bhhdoa.org.au/mailman/listinfo/ck
> 

  reply	other threads:[~2005-08-04 11:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  7:58 [ANNOUNCE] Interbench v0.26 Con Kolivas
2005-08-03 12:01 ` [ck] " Gabriel Devenyi
2005-08-03 12:03   ` Con Kolivas
2005-08-03 23:25     ` Peter Williams
2005-08-03 23:25       ` Con Kolivas
2005-08-03 23:34         ` Con Kolivas
2005-08-04  0:04           ` [ANNOUNCE] Interbench 0.27 Con Kolivas
2005-08-04 11:44             ` Gabriel Devenyi [this message]
2005-08-04 11:46               ` [ck] " Con Kolivas
2005-08-04 12:05                 ` Gabriel Devenyi
2005-08-04 12:04                   ` Con Kolivas
2005-08-04 12:19                     ` Gabriel Devenyi
2005-08-06  3:37                       ` Gabriel Devenyi
2005-08-06  4:59                         ` Con Kolivas
2005-08-10 20:45             ` Bill Davidsen

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=42F1FF89.5030903@staticwave.ca \
    --to=ace@staticwave.ca \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moilanen@austin.ibm.com \
    /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