9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roman Shaposhnick <rvs@sun.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "ridiculous benchmarks"-r-us
Date: Fri,  9 Jan 2004 11:40:07 -0800	[thread overview]
Message-ID: <20040109194006.GA28653@submarine> (raw)
In-Reply-To: <0af7b239ace45c567f28524ff95b5613@plan9.ucalgary.ca>

On Fri, Jan 09, 2004 at 10:42:49AM -0700, mirtchov@cpsc.ucalgary.ca wrote:
> Rog at vitanuova already caught how stupid the following article is
> (linked to from slashdot):
>
> 	http://osnews.com/story.php?news_id=5602
>
> It took me much longer -- until I looked at their "C" code (term used
> very loosely) trying to compile it on Plan 9...  There are multiple
> gems in it including ++ on a double, mid-function variable definitions
> (C-code, right?), log10(0.0), impossible to look at I/O, etc.  In
> fact, I'm attaching the benchmark for your viewing pleasure :)

  Benchmarking nowdays, is a real pain in the kazoo, if you know what I
  mean. Benchmarking compiler itself is no way of demonstrating performance
  of the real application where heavily templated library like libm or
  even libc can make all the difference. The trends I've seen seem to be
  quite amusing when compilers are made to recognize parts of the AST
  (including calls to stuff like sqrt and such) and replace them with
  the predefine assembler template. For evert supported combination
  of arch. switches. Painful.

  The interesting part, of course is when we start considering JITs like
  HotSpot for example. Just recently I was quite amused to see what
  JDK 1.4 did for the simplest fibonacci. Quite educational, I might add.
  Somehow, I feel, that for the best performance possible one simply *has*
  consider execution environment with JIT-modifiable code. No way around it.

Thanks,
Roman.


  parent reply	other threads:[~2004-01-09 19:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 17:42 mirtchov
2004-01-09 17:47 ` ron minnich
2004-01-09 18:19 ` Icarus Sparry
2004-01-09 18:37   ` mirtchov
2004-01-09 20:25     ` Sam
2004-01-09 20:29       ` Charles Forsyth
2004-01-09 20:44         ` Sam
2004-01-09 20:44         ` Brantley Coile
2004-01-10  0:37           ` Dennis Ritchie
2004-01-09 20:48         ` mirtchov
2004-01-11  1:02     ` [9fans] 'ridiculous benchmarks'-r-us Joel Salomon
2004-01-09 18:52   ` [9fans] "ridiculous benchmarks"-r-us Brantley Coile
2004-01-09 20:06     ` Tristan Seligmann
2004-01-10  5:06     ` boyd, rounin
2004-01-09 19:40 ` Roman Shaposhnick [this message]
2004-01-09 20:54 ` Atanas Bachvaroff

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=20040109194006.GA28653@submarine \
    --to=rvs@sun.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).