[osg-users] How can we have a single VRAM footprint over multiple contexts/windows/views/camera in a multi-thread safe way?
OpenSceneGraph Users
osg-users at lists.openscenegraph.org
Tue Oct 13 13:36:08 PDT 2020
Hi Robert, thanks for the answer!
--Vaillancourt
On Wednesday, September 30, 2020 at 12:19:14 p.m. UTC-4 OpenSceneGraph
Users wrote:
> Hi Vaillancourt,
>
> The OSG does not provide thread safe sharing of contexts, and OpenGL
> itself doesn't provide it either, so even if we attempted to mutex lock all
> access to GL objects that multi-threaded nature of graphics would step
> around locks we attempted to add. If you want to share contexts then
> you'll need to use single threading.
>
> With the VSG Vulkan objects are per logical device so you can share
> objects on the same hardware in a more user controlled way, one still has
> to take care because the objects aren't generally safe to read/write to one
> has to use explicit synchronization when managing objects to avoid
> threading collisions. The VSG and Vulkan have waaay lower CPU overhead so
> multi-threading is actually far less critical for performance,
> paradoxically as Vulkan is so much better at handling threading!
>
> Robert.
>
>
>
--
You received this message because you are subscribed to the Google Groups "OpenSceneGraph Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osg-users+unsubscribe at googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osg-users/84b58dd1-f9a7-426e-b2bb-4ddfde69ad1en%40googlegroups.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20201013/332a5702/attachment.html>
More information about the osg-users
mailing list