We don't actually do any synchronization as it is traditionally defined. We do some updates when the Renderer is not running, but we don't acquire a lock to do the updates. It happens in other ways to allow for more parallel processing. We do use messages, and it is true that setting many small components will generate more messages. But, that is only one cost of the whole operation. There are ancillary structures that need to be updated, and the cost of that depends on what is changing.
Doug Twilleager Java 3D Team Sun Microsystems >Delivered-To: [EMAIL PROTECTED] >User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7+) Gecko/20020108 >X-Accept-Language: en-us >MIME-Version: 1.0 >Content-Transfer-Encoding: 7bit >Subject: Re: [JAVA3D] Performance of Appearance Changes >To: [EMAIL PROTECTED] > >Mauricio Vives wrote: > > >> Does that make sense? If so, why would building and setting the >> Appearance object be faster than adjusting a few values on an existing >> Appearance object? Thanks for any insight. > >Are you talking about live object ? If yes, then for every change java3d >needs to send an update message and probably synchronize with renderer. >With one big change, one message is send (change everything) and only >one synchronization will happen. Cost of setting particular properties >is quite small compared to cost of synchronization. > >If you are talking about non-living object, I have no idea. > > >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". =========================================================================== 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".
