As far as the original question that I posed about performance, we found the
culprit.
We had a memory leak detection thread running in the background of the
applet. It was making calls to gc() which is why it was chunky. It turns
out that the Java3D performance did not change, but that the java gc()
performance might have changed due to possible changes in the memory
management of the OS itself.
In any case, the code was found and removed, and Java3D performance is back
to where it should be for this test.
Thank you very much for all the suggestions. I will have to make sure that
I keep all of these issues in mind while proceeding.
Adam
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
