Re: [Flightgear-devel] Musings on optimizing Nasal code

2010-09-17 Thread Tim Moore
On Thu, Sep 16, 2010 at 1:28 PM, wrote: > > You just discovered that Nasal is 10x slower than C++ > > code! This is exactly why I prefer core code to end up in C++ in the end. > > I don't think that's a valid interpretation of my results. Consider the > two cases where I achieved a significant pe

Re: [Flightgear-devel] Musings on optimizing Nasal code

2010-09-16 Thread thorsten . i . renk
> The distance_to() method is a pretty standard "great circle" calculation, > and that's exactly its purpose. Are you sure your "faster" version does > the same? Does it yield the same (numeric) results? And besides, in the > visual range direct_distance_to() should be good enough, and it's > certa

Re: [Flightgear-devel] Musings on optimizing Nasal code

2010-09-16 Thread Melchior FRANZ
* thorsten.i.r...@jyu.fi -- 9/16/2010 1:28 PM: > I don't think that's a valid interpretation of my results. Consider the > two cases where I achieved a significant performance gain by replacing > hard-coded structures with my own Nasal code (range animation, > distance_to() method) The distance_to

Re: [Flightgear-devel] Musings on optimizing Nasal code

2010-09-16 Thread thorsten . i . renk
> You just discovered that Nasal is 10x slower than C++ > code! This is exactly why I prefer core code to end up in C++ in the end. I don't think that's a valid interpretation of my results. Consider the two cases where I achieved a significant performance gain by replacing hard-coded structures w

Re: [Flightgear-devel] Musings on optimizing Nasal code

2010-09-16 Thread Erik Hofman
On Thu, 2010-09-16 at 08:59 +0200, Anders Gidenstam wrote: > I think a bigger issue might be that both getChild() and getNode() > create and return a hash object that is only used once here before > becoming garbage. Since this was loop with many iterations a good deal of > garbage was created so

Re: [Flightgear-devel] Musings on optimizing Nasal code

2010-09-15 Thread Anders Gidenstam
On Wed, 15 Sep 2010, Erik Hofman wrote: > After thinking about it I think that in the second case the property > tree is being walked trough by the C++ code while in the first case it's > done in Nasal. You just discovered that Nasal is 10x slower than C++ code! > This is exactly why I prefer core

Re: [Flightgear-devel] Musings on optimizing Nasal code

2010-09-15 Thread Erik Hofman
thorsten.i.r...@jyu.fi wrote: > I've just spent a session optimizing performance of the weather dynamics > routines, and I have largely done so by analyzing the performance of > elementary Nasal function calls and making use of my findings (and also by > dispensing with the pretense of elegant codi

[Flightgear-devel] Musings on optimizing Nasal code

2010-09-15 Thread thorsten . i . renk
I've just spent a session optimizing performance of the weather dynamics routines, and I have largely done so by analyzing the performance of elementary Nasal function calls and making use of my findings (and also by dispensing with the pretense of elegant coding). I was rather gratified to see t