Sign in to follow this  
Nairou

OpenGL Expense of modifying/replacing loaded textures

Recommended Posts

Nairou    430

How well does OpenGL (3.2, if it matters) handle modifying or replacing textures that have already been uploaded to the GPU?

 

I always had the impression that messing with textures was always much more expensive than replacing VBO data, even if the texture is far smaller in byte size, but I'm starting to think this might not be the case.

 

Is there perhaps a list somewhere that shows what sort of operations are most expensive in OpenGL?

 

For context, I'm working on a terrain system where the terrain colors can change frequently. I figure I can either do texture mapping, and modify the texture pixels, or put the color in the terrain vertices and rebuild the VBO for each change. I'm accustomed to continually rebuilding dynamic VBOs for other tasks, but in this case I am thinking that a texture would be a lot less data to upload than the block of geometry.

 

Share this post


Link to post
Share on other sites
cr88192    1570

you may need to test this...

 

for example, I have had reasonably good success doing things like streaming videos into textures (such as 8 video streams at a time), but on some older hardware (~ 10 years ago), this would put some hurt on the performance.

Share this post


Link to post
Share on other sites
mhagain    13430
This is one of those things that could be reasonably cheap or could be horribly expensive, depending how you need to do the update, what formats you use, and so on.

First thing is to batch up your updates. A single glTexSubImage call updating the entire texture will perform better than lots of calls updating tiny subrects of it.

Try to divide your workload into updating, then drawing. If you need to update/draw/update/draw/etc your performance will tank, especially on Intel or AMD hardware (NV tolerates this pattern better, but it's still a slower path).

Watch your formats; you absolutely must match the data you feed to glTexSubImage with the drivers preferred internal representation. Normally that means using a BGRA format. Don't fall into the trap of using RGB because you think it will "save memory" - the driver will need to unpack and reswizzle the data as a slow software process and again your performance will tank. Experiment with different values for the type param - GL_UNSIGNED_INT_8_8_8_8_REV can work well here.

Finally, and if you can schedule the update for a few frames ahead of when the texture is needed, consider using a PBO to get an asynchronous transfer. If you need to update in the same frame as the texture is used don't bother with the PBO - it's just extra overhead.

Share this post


Link to post
Share on other sites
L. Spiro    25619

The OpenGL drivers are one factor, which means it depends on a very wide number of factors, so what works best for you may not for another.

 

One universal truth however is that if you update a texture while it is still being used by the GPU the GPU will perform a synchronous flush in order to allow you to update the texture safely on the CPU side.

 

This will be terrible performance no matter what API you use or hardware you have etc.

 

If you need to update the texture frequently or if your updates always cover the whole body of the texture, you should double-buffer the texture, or possibly triple-buffer it.

 

 

L. Spiro

Share this post


Link to post
Share on other sites
mhagain    13430

One universal truth however is that if you update a texture while it is still being used by the GPU the GPU will perform a synchronous flush in order to allow you to update the texture safely on the CPU side.

 

I would hope that in this case drivers are at least reasonably intelligent and copy off the data to temp storage for updating at a later time when the resource is no longer in use (similar to the D3D10+ case for UpdateSubresource where there is contention, although unfortunately OpenGL doesn't seem to specify a behaviour here).

Share this post


Link to post
Share on other sites
cr88192    1570

One universal truth however is that if you update a texture while it is still being used by the GPU the GPU will perform a synchronous flush in order to allow you to update the texture safely on the CPU side.

 

I would hope that in this case drivers are at least reasonably intelligent and copy off the data to temp storage for updating at a later time when the resource is no longer in use (similar to the D3D10+ case for UpdateSubresource where there is contention, although unfortunately OpenGL doesn't seem to specify a behaviour here).

 

when messing around with multithreaded OpenGL and texture uploading (with the rendering and texture-uploading being done in different threads), I observed some interesting behaviors here:

the glTexImage2d() or glCompressedTexImage2d() calls were completing immediately;

within the main render thread, it would often be up to several seconds later until the texture image actually appeared (otherwise, it would be the prior contents and/or garbage).

 

typically, having the uploader threads call glFinish() would cause them to stall temporarily, but results in the next frame in all of the textures being correct.

 

judging by this, I suspect the driver is lazily updating the textures in this case.

 

 

I am less certain what happens in the single-threaded case, but have made another general observation:

if you do something, and try to immediately make use of the results, there will be a stall.

 

this seems to happen with both VBOs and also things like occlusion queries, like there is a delay between when the upload call is made, and when it can be bound or used.

typically, in my case this means "batching" things and doing them in a partly interleaved order (say, all the draw requests for occlusion queries before fetching any of the results, or uploading all the updated VBOs before the rest of the drawing pass begins, ...).

 

granted, I am not sure how much of this is driver/hardware specific. in this case, I am using a GeForce GTX 460...

Edited by cr88192

Share this post


Link to post
Share on other sites
Nairou    430

If you need to update the texture frequently or if your updates always cover the whole body of the texture, you should double-buffer the texture, or possibly triple-buffer it.

 

Very interesting, I didn't know textures could be double-buffered. Do you have any links on doing this in OpenGL?

Share this post


Link to post
Share on other sites
mhagain    13430

If you need to update the texture frequently or if your updates always cover the whole body of the texture, you should double-buffer the texture, or possibly triple-buffer it.

 

Very interesting, I didn't know textures could be double-buffered. Do you have any links on doing this in OpenGL?

 

There's no specific OpenGL technique for this.  Instead you allocate two textures (let's call them 0 and 1), then update texture 0/draw using texture 1 and vice-versa on alternate frames.

Share this post


Link to post
Share on other sites
Nairou    430

There's no specific OpenGL technique for this.  Instead you allocate two textures (let's call them 0 and 1), then update texture 0/draw using texture 1 and vice-versa on alternate frames.

 

But I'm assuming you can't have both textures bound for this to work, right? If you updated texture 0, and the shaders knew to only sample from texture 1 this frame, would the GPU really know that texture 0 wasn't accessed? Or would you still end up with a synchronous flush from updating texture 0?

Share this post


Link to post
Share on other sites
cr88192    1570

There's no specific OpenGL technique for this.  Instead you allocate two textures (let's call them 0 and 1), then update texture 0/draw using texture 1 and vice-versa on alternate frames.

 

But I'm assuming you can't have both textures bound for this to work, right? If you updated texture 0, and the shaders knew to only sample from texture 1 this frame, would the GPU really know that texture 0 wasn't accessed? Or would you still end up with a synchronous flush from updating texture 0?

 

AFAICT, "the magic" happens when you try to bind and draw using the texture or similar.

so, if the texture is updated but never used, there wont really be a stall (and the driver will update it later at some point).

Edited by cr88192

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  

  • Similar Content

    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
    • By C0dR
      I would like to introduce the first version of my physically based camera rendering library, written in C++, called PhysiCam.
      Physicam is an open source OpenGL C++ library, which provides physically based camera rendering and parameters. It is based on OpenGL and designed to be used as either static library or dynamic library and can be integrated in existing applications.
       
      The following features are implemented:
      Physically based sensor and focal length calculation Autoexposure Manual exposure Lense distortion Bloom (influenced by ISO, Shutter Speed, Sensor type etc.) Bokeh (influenced by Aperture, Sensor type and focal length) Tonemapping  
      You can find the repository at https://github.com/0x2A/physicam
       
      I would be happy about feedback, suggestions or contributions.

  • Popular Now