Skip to Main Content

Java SE (Java Platform, Standard Edition)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

CPU killer

843799Sep 3 2001 — edited Sep 3 2001
It seems that J3D utilises 100% of available CPU in interactive apps to maximise rendering etc..
This is fine if the Java3D app is the only important process currently executing.
However I am trying to use J3D to develop interactive representations of data mining processes.
The DM alg and J3D visualisation are run as separate processes with socket level coupling (Yes, they must be separate processes).

The result is that the Java3D app sucks up approx. 95% of CPU (over 50 min period even with the
J3D thread priority minimised), this leaves little CPU for the mining alg. to crunch data.

I've had a good dig and there doesn't seem a way to effectively reduce the J3D CPU monopoly. Any idea's would be greatly appreciated, I really don't want to start over in OpenGL :(

TIA
Aaron

Comments

Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 1 2001
Added on Sep 3 2001
2 comments
120 views