Sign in to follow this  
digitalgibs

OpenGL glBufferSubDataARB performance issues

Recommended Posts

Can anyone tell if there is a better way? Is it the number of calls to glBufferSubDataARB() that's killing me or the number of VBO's ?!? I'm working on an opengl project that has potentially hundreds of objects (around 300-400 objects) animated on the CPU. Each one is roughly 300-900 triangles. Unfortunately I can't batch them into a single draw call as each object may contain unique shader parameters. Right now I'm pre-allocating VBO memory for each object using glBufferDataARB( GL_ARRAY_BUFFER_ARB, numBytes, verts, GL_DYNAMIC_DRAW ) and then updating all VBOS using glBufferSubDataARB( GL_ARRAY_BUFFER_ARB, 0, numBytes, verts ) before rendering the objects. I'm told that this is the fastest way to update but for some reason this is killing my performance. If I comment out this update call and just loop through all other code (cpu animations, visible object determination, etc) it runs at crazy frame rates (120+ fps), but including the update drops it down to the teens. NOTE: To avoid fill-rate times from effecting my tests, I disabled the actual draw calls. Only CPU code and VBO updates were being processed here.

Share this post


Link to post
Share on other sites
Try mapping buffers, try to have fewer buffers with more than one triangle group in each (and use offset for drawing), and try to have several sets of them or use glBufferDataARB(..., 0, ...).

glBufferSubDataARB can do, but is not required to, the transfer to the card asynchronously. What it can't do is to do the memory copy to its own buffers asynchronously, as you could in theory delete the pointed-to memory the next microsecond after the function call returns. Thus it will always have to have some additional delay compared to mapping the buffer.

Your second issue is binding buffers, which is not as trivial on the driver side as you may think. Doing that many hundred times per frame can be a problem. Indexing into fewer buffers is cheaper.

The third issue is stalls. Drawing cannot happen before all data has been transferred, and transfers to the same memory can't happen before all draws that use it have finished. The driver will schedule asynchronously as much as it can, but it can't do much in such situations if it doesn't know what's safe to discard and when.
This can be solved by explicitely having 2-3 sets of buffers (so it will draw from one while you upload the other) or simply by calling glBufferDataARB with zero size before uploading the next buffer, which tells the driver "I won't be using the old contents any more, so throw it away once you're done, and store my new data elsewhere in the mean time".

Share this post


Link to post
Share on other sites
Thanks samoth. Maybe I'll try to create one big VBO and reserve partitions for each object, then render using offsets. I wonder if bandwidth is an issue here as well since I'm using a interleaved vertex structure and not separate arrays.

// vertex structure (68 bytes)
vec3f pos;
vec2f st[2];
vec3f tangents[3];
unsigned char color[4];

At an average of 600 verts x 300 objects x 68 bytes, I'm looking at 12MB per frame of uploads... =( That sounds like a lot, but I don't know what is considered reasonable for OGL1.5+ compatible video card.

Share this post


Link to post
Share on other sites
question.. If i group many objects into one VBO how would I assign the offset?!?

// object[0]
glVertexAttribPointerARB(..., 0); // vertex.pos
glVertexAttribPointerARB(..., 12); // vertex.texcoord

// object[1] ?? is the following valid ??
glVertexAttribPointerARB(..., 0 + firstVertexOffset); // vertex.pos
glVertexAttribPointerARB(..., 12 + firstVertexOffset); // vertex.texcoord

or would I always bind (0 and 12) and use offsets in my index buffer?

object[0].indexes = { 0, 1, 2, 3 }
object[1].indexes = { 4, 5, 6, 7 }
etc...

Share this post


Link to post
Share on other sites
FYI for anyone following this thread. It unfortunately didn't make a very big difference in performance to combine VBO's. =(. I guess the way I was handling the data was fairly optimal to begin with so batching the objects into a single VBO was a negligible boost at the cost of much less flexibility (hard to add/remove objects easily without another manager or brute re-allocations to close the fragmentation).

I think that I may have simply run into a bandwidth issue with my card =(. I did a test with around 300 objects which totaled close to 6.2MB of vertex buffer updates but only a few bytes of index buffer updates. The frame rate was running around 25fps-35fps (no rendering, only updates) which means:

(6.2)MB per frame x (25 to 35)fps = 155MB/s - 217MB/s upload...

video card:
NVidia GeForce 8600M GS

Wikipedia claims a memory bandwidth of 12.8 to 22.4 GB/s... Ofcourse AGP1x and PCI are in the range of 150-250MB/s so this is likely the problem and not the video card.

[Edited by - digitalgibs on July 27, 2009 2:05:31 AM]

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Announcements

  • Forum Statistics

    • Total Topics
      628367
    • Total Posts
      2982284
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now