Hi Adrain, On 2/1/07, Adrian Egli <[EMAIL PROTECTED]> wrote:
very interesting talk. i developped once a system to syn threads, and rendering in parallel for multi windows. it has to work also in single thread, if we have a single core cpu, it isn't faster doing things multithreaded as you know.
Well there are cases when multi-threaded on a single core can be faster than single-threaded, particularly when IO is involved. I haven't done with the new threading model on a single core single screen system yet.
it was easy to add an user thread, without thinking about the syn. etc. so
What do you mean by syn. etc?
may question would be how do you implement it, and would it be possible to run also in n-thread model, can i add my own thread (simulation, so on) without thining about openscenegraph threading, crash, race condition, so on
Added extra threads to do other operations is possible, how easy depends on the nature of the operations that you are conducting. One thing I have considered is adding support for running the read only camera threads alongside configurable end user read only operations. These operations would need to complete within a frame though, otherwise they'd stall the main loop - as you can't advance a frame till you've finished doing all read only ops. Although I must add I'm bending this rule a bit in new thread per camera model, as the graphics thread can continue running even after the read-only section has completed, with the proviso that the bits its left reading from are static objects not changed during the update phase of the scene graph. Was it read only threaded operation what you were thinking of? BTW, one could make non read only op, read only by caching the modifications so that they are applied during the update phase. Is this the type of thing you were wondering about? Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
