Re: Last Quesa is very slow

[James W. <ja...@fr...>]

Sauro Agostini wrote:
> Using the latest Quesa we found that it is very slow than the old 1.8 
> version and previous versions, especially with polygons and general 
> polygons.
> 
> The problems is evident with our programs, where using the latest 
> version of Quesa, navigating is very slow using any renderer.
> 
> We tested different versions of Quesa on different computers using 
> Geom Test with the following results:
> 
> 
> Test                                                MultiBox 
> Quesa Logo     MultiBox        Quesa Logo
> 						   Interactive 
> Interactive       OpenGl         OpenGl
>                                                         FPS 
> FPS           FPS            FPS
> 
> Last Quesa on iMac Intel Core duo 1.83 GHz             12 
> 1030           11             2500
> Last Quesa on G5 Dual 1.8 GHz                           9 
> 630           11             1500
> 
> Quesa 1.8  on iMac Intel Core duo 1.83 GHz             36 
> 970          -----          -----
> Quesa 1.8  on G5 Dual 1.8 GHz                          26 
> 720          -----          -----
> 
> Old Geom Test 2003 on iMac and Rosetta                 18 
> 500          -----          -----
> Old Geom Test 2003 on G5 Dual 1.8 GHz                  28 
> 730          -----          -----
> 
> 
> Practically the latest version is faster using OpenGl and Quesa Logo, 
> but it is very slow with the MultiBox  model, independently of the 
> kind of renderer, where last Quesa for Intel is slower than Quesa 1.8 
> emulated with Rosetta!
> 
> Also with our programs we have similar results, with the latest 
> version that is 3 times slower than Quesa 1.8 and previous versions 
> (12  FPS versus 36 FPS).
> 
> Any suggestions?

Are you sure you're comparing builds made with the same compiler and 
optimization options?  I am a little skeptical, because outside the 
OpenGL renderer, I think most recent changes have been intended to 
improve performance.

Besides my previous suggestion to try Shark, you could use cvs to try to 
narrow down the problem.  That is, check out the sources as of various 
dates between 1.8 and now, to try to discover when a slowdown happened.
-- 
   James W. Walker, Innoventive Software LLC
   <http://www.frameforge3d.com/>