you misunderstood the meaning of the '15% figure' - it's not about CPU load, but about CPU potential if the code would be more optimized .On 2004-09-10 02:46, symbiote wrote:
... POVRay uses more than 15%, also compiling stuff takes more than 15%,...
I dunno POV in detail, but from all I've read about it I'm rather convinced that it's far from highly optimized graphic routines (and assembly wizzardry)

That kind of coding is not really my cup of tea, but I've learned programming in a time when it was absolutely essential that you found ways to make your code perform faster.
CPUs were clocked from 8-30 MHZ those years and I still occasionally use apps from this time which easily outperform M$'s crap on a CPU running at least 30 times faster.
So the estimation that a routine can be optimized for a factor of 50 isn't totally absurd

You'll find the same information in any 'classic' book about programming algorithms and strategies.
The current public opinion about this subject is something like 'well we have fast CPUs, so there's no need to fiddle around - we don't have time for this...'
As wrong as can be - there's a physical limit in CPU clocking and it's almost reached.
Or are you seriously expecting a 50 GIG P4 anywhere in near future ?
do you have any idea what it takes to transfer a product consisting of a 150 man years developement effort to a new platform ?On 2004-09-10 03:47, R-type wrote:
It's a sweet idea, if I was Creamware I would be looking at recompiling their awesome range of plugins to a new platform. ...
And in case you didn't notice: the math core routines aren't by Creamware, but by Analog devices...

You may add another 50 man years to transfer (better re-engineer) that part of the system.
But while it may be possibly to hire some clever dudes for the GUI stuff, you will just fail on the latter issue due to the lack of people capable to deal with that kind of coding.
cheers, Tom
<font size=-1>[ This Message was edited by: astroman on 2004-09-10 05:59 ]</font>