From: "Raj Vaidya" <[EMAIL PROTECTED]> Sent: Friday, December 28, 2001 2:49 PM
> To All Ye Thread Gurus: Well, this message is obviously not addressed to me, but I'll respond anyway. > Is fiddling with threads worth the trouble in a Java3D App.? In general, I think it is. It's a mysterious business, but there seem to be some things that work reliably. > For example, at the click of a Swing button my app. does > very highly numerically intensive computations to create > a geometry and subsequently makes it *live*. At the time > when the geometry is being created, I would like all > CPU resources to be dedicated to just that and minimally, > if at all, to anything else. Would the resources allocated > to the various threads(?) ( viz. Swing thread, the Java3D > renderer thread, behavior threads etc) grossly affect that > allocated to numerical computations (FLOPS). If so, are there > safe/adventurous ways of handling the problem with/without > regard to portability ? My approach to this would be purely ignorant application of techniques that have kept me out of trouble in the past. My guiding principle for a happy life is to do everything important inside a processStimulus(. . .). Then I would put a j3d thread priority JSlider on it (like the one in the example Kelvin posted here a few weeks ago) and see how it ran. This, I think, would have the effect of freezing the rendering while your geometry calculation was going on, and Swing or system resources would be starved or glutted depending on the setting of the j3d thread priority slider. I'd be very reluctant to spawn my own threads to do anything important. Advice is usually worth what you pay for it. Fred Klingener Brock Engineering =========================================================================== 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".
