CPU killer

843799

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

843799

Try creating your own custom canvas3D (really easy to do) and add your own code in preRender() to send the rendering loop to sleep for as long as you want per frame. This should give your other threads 100% for that period of time (but of course framerate will suffer).

843799

Thanks, works fine.
However this does raise the problem of ineffeciency when running on the multiprocessor servers, instead of locally from my PC. However the work around is good and allows me to demonstrate effectively.