On Wed, 18 Apr 2001, Paul Pantera wrote:
> But after you use it, you just throw it away. You never need to keep
> a GeometryInfo (or Stripifier or NormalGenerator) around. It's usually
> only used during setup.
Yes, but with normal gc (not -Xincgc) this memory is never returned to OS.
And full gc takes a lot of time when it will happen at last (I prefer more
frequent shorter pauses).
> You mean the setup time is faster, not the rendering time, right?
> If you use the Stripifier and pull out an un-indexed GeometryArray,
> the rendering performance is going to be hard to beat.
I can stripify my data optimally. Stripifier sometimes make small mistakes
even in simple cases (like sphere or grid/height map).
> If you use the native data types of GeometryInfo, it will consume
> less memory by using your data instead of copying it. For example,
> use an array of Point3f for your coordinate lists. This is
> documented in the javadoc for GeometryInfo:
I always use float[] for coordinate lists.
I think that GeometryInfo is a great thing. But there is no doubt it is
heavyweight. If I can construct simple shape myself, I will do that - gc
is really a poor little animal which has to be protected inside java3d
apps.
Artur
===========================================================================
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".
