Joerg Scheurich aka MUFTI wrote:
Performer maybe used the other processors too, while XJ3D only used
one processor ?
BTW: SGI machines have a tool "gr_osview" which can be configured
to track the activity of a running SGI machine, including
multiple CPUs and graphics.
That's what we were using. Despite claims otherwise, Java3D is running
not multi-threaded internally. With 4 CPU's when running _any_ Java3D
application on the box, it would max one CPU and leave the rest
completely idle. This appears to be an SGI-specific problem because my
development machine is dual-CPU and J3D correctly spreads the load
across both processors here. We checked the details of the latest JVM
and it is using native threads, so there's something else really wrong
with the SGI port of Java3D right now. I couldn't really recommend
anyone else using it given this experience.
--
Justin Couch http://www.vlc.com.au/~justin/
Java Architect & Bit Twiddler http://www.yumetech.com/
Author, Java 3D FAQ Maintainer http://www.j3d.org/
-------------------------------------------------------------------
"Humanism is dead. Animals think, feel; so do machines now.
Neither man nor woman is the measure of all things. Every organism
processes data according to its domain, its environment; you, with
all your brains, would be useless in a mouse's universe..."
- Greg Bear, Slant
-------------------------------------------------------------------
===========================================================================
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".
