From: petethebloke@...
Date: 2006-07-26T18:45:06+09:00
Subject: Re: For performance, write it in C

It might be interesting to see how Java fares too - another route
again.

Pete


benj...@fysh.org wrote:
> Peter Hickman gave a very good article about prototyping in a scripting
> language, and then re-coding in c:
>
> *snip*
>
> > If you really really want that performance boost then take the following
> > advice very seriously - "Write it in C".
>
> I totally agree that with the current state of the art, this is the
> right approach.
>
> Maybe it doesn't need saying, but I'm going to... in the vasy majority
> of applications, almost all of their run time is a tiny wee small
> fraction of the code. This is the part that I would write in c (or c++).
> The vast majority of the code (and it's not there just for fun, it's
> still completely important to the application) will use a vanishingly
> small fraction of processor time. This is the bit that I would probably
> leave in Ruby.
>
> People talk about the 80:20 principle, but in my experience it's much
> more like 99:1 for applications. 99% of the code uses 1% of the run
> time. 1% of the code consumes 99% of the run time. That could be the
> signal processing and graphics heavy applications that I have
> experienced though.
>
> Thanks for the comparison, it was great. And thanks for the very nice
> pre-generation of look up tables in perl idea. Nice.
> 
> Cheers,
>   Benjohn