All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Gabriel Devenyi <ace@staticwave.ca>
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, 4 Aug 2005 21:46:13 +1000	[thread overview]
Message-ID: <200508042146.13710.kernel@kolivas.org> (raw)
In-Reply-To: <42F1FF89.5030903@staticwave.ca>

On Thu, 4 Aug 2005 21:44, Gabriel Devenyi wrote:
> Hi Con,
>
> You must hate me by now...

No. A bug report is a bug report. I hate the fact that I coded up 2000 lines 
of code and am still suffering from a problem in the same 10 lines that I did 
in version .01. PEBKAC. 

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

Anyway Peter Williams has promised to fix it for me (yay!).

> 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.

> 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!

I have to think about it. This seems a problem only on one type of cpu for 
some strange reason (lemme guess; athlon?) and indeed leaving out the sleep 1 
followed by the check made results far less reliable. This way with the sleep 
1 I have not had spurious results returned by the calibration. I'm open to 
suggestions if anyone's got one.

Cheers,
Con

  reply	other threads:[~2005-08-04 11:50 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             ` [ck] " Gabriel Devenyi
2005-08-04 11:46               ` Con Kolivas [this message]
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=200508042146.13710.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ace@staticwave.ca \
    --cc=ck@vds.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.