Doug Gehringer wrote:
...
>
> If gc is the culprit, then you can speed things up by reducing your memory "burn
> rate". Try to reuse objects instead of creating them with each frame. Since you
> are modifying transforms with each frame, make sure you re-use the transforms
> instead of creating new ones.
>
> Early in the Java3D development process the team was able to significantly
> increase frame rates and decrease "jitter" by carefully managing memory.
...
I have the same problem with the gc. Since I know, that these short pauses
are caused by the gc, I try to reduce the burn rate. I do not create new objects
while runtime. But the gc starts to collect, if there are setTransform(...) commands.
I use a Thread to control a ball, running on a track. If I disable eveything in the
Thread so that it starts and then sleeps for 25ms, there is no garbage collection.
If I add three setTransform(...) commands, the gc frees about 11650 objects,
600kB in 80 ms, every 10ms!
Perhaps it is the setTransform() method, which does not re use variables?
Gerd Trautner
--
Trautner Gerd
Bahnhofstr. 39
A - 4230 Pregarten
--------------------------
http://yuri.weirdoz.org/pd
=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 3D Home Page: http://java.sun.com/products/java-media/3D/
