http://www.sys-con.com/story/print.cfm?storyid=45250
Any comments?
Thanks
Gaurav
Roedy Green - 16 Jun 2004 13:19 GMT
>http://www.sys-con.com/story/print.cfm?storyid=45250
the key is obviously the improved method calls. This is done though
inlining. The big advantage hotspotting has is knowing what to
inline. Inlining everything just gobbles up RAM with no payback.

Signature
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.
David Hopwood - 16 Jun 2004 19:57 GMT
>>http://www.sys-con.com/story/print.cfm?storyid=45250
>
> the key is obviously the improved method calls. This is done though
> inlining. The big advantage hotspotting has is knowing what to
> inline. Inlining everything just gobbles up RAM with no payback.
Although note that gcc was run with -O2, which does not inline at all.
gcc -O3 would have been a more reasonable comparison.
A more interesting question: why does anyone pay any attention to
microbenchmarks?
David Hopwood <david.nospam.hopwood@blueyonder.co.uk
Jonas Geiregat - 16 Jun 2004 21:35 GMT
> http://www.sys-con.com/story/print.cfm?storyid=45250
>
> Any comments?
>
> Thanks
> Gaurav
They forgot gcj.
Keith A. Lewis - 17 Jun 2004 01:12 GMT
>http://www.sys-con.com/story/print.cfm?storyid=45250
>
>Any comments?
Yeah, yahoos that don't proofread their subject line probably don't
have a clue. You also misspelled far. I followed up to comp.lang.c++
so you can get properly flamed for being a troll.
Dave Monroe - 17 Jun 2004 13:27 GMT
> http://www.sys-con.com/story/print.cfm?storyid=45250
>
> Any comments?
>
> Thanks
> Gaurav
Does 'apples and oranges' ring a bell?
Big cycle suckers can be better - unless you need small and efficient.
The answer is: it depends.
Benchmarks are management fodder, and often the source of bad decisions.
Roedy Green - 17 Jun 2004 16:20 GMT
>Benchmarks are management fodder, and often the source of bad decisions.
Focusing on benchmarks is often being penny wise and pound foolish.
What counts is getting the product out the door on time, bug free on
budget, and doing that release after release. Whether it runs 5%
faster nobody will notice.
In fact for many programs it has to run 100% faster for it to be even
psychologically noticeable.
If you have a bottleneck you will get far more return on your time and
money by profiling and tuning the critical section, especially
choosing a smarter algorithm, than you ever will by backing off to a
more manual language that introduces far more problems than it solves.

Signature
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.
EventHelix.com - 17 Jun 2004 13:33 GMT
Not sure if GCC is the best optimized compiler. May be these tests
should be rerun with MS C++ compiler on Windows and Intel C++ 8.0 on
Linux.
Sandeep
--
http://www.EventHelix.com/EventStudio
EventStudio 2.0 - Generate Sequence Diagrams (no drawing required)
JTK - 18 Jun 2004 05:45 GMT
> http://www.sys-con.com/story/print.cfm?storyid=45250
>
> Any comments?
Just one:
BAAAAAAAAAAAAAAAAAAAAAAAAAHAHAHHAHAHAHAHHAAAAAAAAAAAAA!!!!!
Jesus von Neumann CHRIST you Javapologists, GIVE IT THE HELL UP ALREADY!
Anon Amous - 18 Jun 2004 07:33 GMT
Consistently Stupid,
thank you for another meaningless comment.
> > http://www.sys-con.com/story/print.cfm?storyid=45250
> >
[quoted text clipped - 5 lines]
>
> Jesus von Neumann CHRIST you Javapologists, GIVE IT THE HELL UP ALREADY!