Hi Bill,

I believe you are seeing the effect of one of the fixes to ClassBuilder.
When you add new objects, 
Wonderland creates new classes for them. This may eventually involve
recompilation of the classes 
and with the changes I posted this will incur a penalty of one full GC per
class recompiled [*]. It is 
likely that if you are creating many new objects this is the effect you are
seeing (a message tally 
should show this pretty clearly).

[*] Yes, this GC is needed. I thought long and hard about avoiding it but it
can only be avoided if you 
are willing to risk apparently random crashes in some obscure but perfectly
possible situations. The 
only safe way is to either add that GC or to fix the way #become works - and
I wasn't in the mood for 
the latter.

Cheers,
  - Andreas

> Hello all,
> 
> I grabbed the most recent 3.4 alpha and loaded my code into it.  
> There is a noticeable slow-down in my Alice-based experiments, 
> which seems to be most severe as new objects are added to the 
> wonderland.  I'm using Alice as a retained mode engine, with the 
> camera controls and script editor hidden.
> 
> The visual feedback offered by PluggableButtonMorph seems to be 
> spread over more time than in 3.2.  That lead me to look at 
> framerates.  Absent a running wonderland, the frame rate (in 3.4a) 
> on my P4 at home is being reported as roughly 470 frames per 
> second???? That's vs. 45 fps or so in 3.2.  Is that real, or is it just 
> a bug in the frame rate morph?  With the wonderland, frame rates 
> are reported as 25-40 fps vs. similar ranges in 3.2, though there's 
> more of a penalty for doing certain things in 3.4a.
> 
> I did _not uninstall/reinstall Balloon3D.  Should I have done so?  I 
> used SM to install a few things, including the RB and Connectors.
> 
> Comments/suggestions?
> 
> Bill
> 
> Wilhelm K. Schwab, Ph.D.
> bills at anest4.anest.ufl.edu
> (352) 846-1285
> 

-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!