OpenGL Low framerate during first seconds

Recommended Posts

Hi gamedev !

I'm facing a really strange performance issue occurring during the first seconds of my app.
When launching the app, three scenarios:

  • Some erratic frames at the very beginning, then 70+fps.
  • Some erratic frames at the very beginning, then ~12fps, then, after a few seconds, BAM, 70+fps.
  • Some erratic frames at the very beginning, then stuck at ~12fps.

Camera is static, so is the scene.

I used nsight to try figure out what's happening, especially in case 2 where I can see what are the differences.
When it's rendering at ~12fps, some glDrawRangeElementsBaseVertex/glDrawArrays calls takes a lot of time, some SwapBuffers calls too, and after switching to "cruise speed", those calls are taking a more moderate amount of time:

Here is a capture of a nsight session timeline:


1->erratic framerate at the beginning


3->stable and high framerate

Memory usage is the same in all cases.
CPU Usage is a bit higher when stuck at ~12fps, but nothing remarkable.

My scene is really simple (only a few cubes), but I use a lot of post process (SSAO, SSR). Reducing the framebuffer size to a smaller one doesn't change anything (although top speed is faster).
I also tried to disable all my post process, issue is still there but case 1 is the most common.

it is really similar to what's described in this post, although I'm not using vsync at all (double checked code, and also forced vsync off with the nvidia control panel) nor SDL.

I also tried to put some glFlush()/glFinish() here and there in my code, without success.

A few specifications:
OS: Windows 7
CPU: Core I7 6700
GPU: Nvidia 560Ti
Drivers: 385.41
I'm stuck with this issue for months now, it's driving me crazysick.gif

Thanks for any help/advice/question/test to make

Edited by CrashyCartman

Share this post

Link to post
Share on other sites

Throwing a dart in the dark here...

When you launch your app, everything is cold. Driver has to setup who knows what for your application in the background, compile your shaders, pass stuff to the GPU, etc. Once all of this stabilizes (say, you've used all your shaders at least once for actual drawing), everything runs as expected.

Drivers do a lot of lazy loading, specially for OpenGL where there are tons of paths to do the same thing and they might require slightly different things. You might ask the driver to compile a shader, and bind a bunch of state, but the driver might only actually do that work when you actually draw with any of them set, until that happens, the driver can just "pretend" it did what you told it to do. It saves up work if you say, change the raster state 3 or 4 times until you actually draw with it. Driver makers prefer to assume you're stupid rather than taking the backlash of XYZ big game that doesn't works as fast as the competition.

Also if you're using any kind of "managed language" (something that runs on top of the CLR or a JVM for instance), those have to do a lot of setup work too, usually concurrently with your application (say, HotSpot, a JVM, can run your code in interpreted mode, while it is compiling it at the same time, then later replace it with the compiled code when it finishes).

This is also true of native languages to a lesser extent for different reasons, big exe/dll/so/dylib/etc might take a while to load and the important bits might take a while until  they hit the CPU caches.

Share this post

Link to post
Share on other sites

Thanks for the answer:)

I know driver must be busy after resource loading, and could accept having some long frames at start, but in this case, 33% of time I've got a game completely unplayable.

I also made tests removing all of my threads, just to see if it was a concurrency issue, and unfortunately it didn't change anything.

Everything is in c++, no managed code.

I may add that if I run the exe by doing "Nsight/Start Graphics Debugging", everything is ok, of course I have some hiccups at start but then, game runs smooth every time.


Share this post

Link to post
Share on other sites

Ah right, I misunderstood the problem. Just in case, hows GPU memory usage? Most 560 have 1Gb, you might be threading in a line where sometimes you're running out of GPU memory and sometimes you don't, for whatever reason.

You can check it in a nice graph with something like MSI Afterburner or GPU-Z.

Check system memory too just in case.

Edited by TheChubu

Share this post

Link to post
Share on other sites

Alright here are the results of my quick benchmarks made using GPU-Z to track gpu memory.

During loading and the first erratic frames, gpu memory is full (1000MB).

After that, it falls down to around 800 MB, framerate is stable but low.

And if after a few seconds framerate increases, GPU memory goes to around 950MB, if not, it stays at 800MB/low fps forever.

So there is a real correlation between both memory usage & performance.

I tried changing the format of the few FLOAT16 RGBA  FBOs I use to RGBA8 in order to reduce size, but it didn't change anything to memory usage, which is strange.

System memory shows the same relationship between memory & framerate.


1: first run, app runs fine at 70 fps

2: second run, app is stuck at 12 fps.

3: third run, same as 1

As you can see, the difference is small (100 MB) but noticeable.

Thanks for trying to help me :)

Share this post

Link to post
Share on other sites

Are you running in fullscreen at 4k or something? Say, on my Windows 7 desktop I get around 100Mb of GPU memory used constantly, the rest is available. So if you have anything else running that hogs VRAM, close it (games, videos, chrome, whatever). See how much your application is actually taking. Try running it in a 800x600 window.

Share this post

Link to post
Share on other sites

Running in 720p, and yes, I find this crazy to have so much vram used, should have tracked that before. I use only a few small textures for the moment, no reason to have so much memory used.

Thanks for your help, I'll check what's wront and post the solution here :)

Share this post

Link to post
Share on other sites

Alright, here are the various causes :)

  1. I had some extra large (8k) textures I used to generate small sdf font textures, but never removed them after sdf generation.
  2. My shadow maps are packed into a single big GL_R32F atlas, and the depth buffer of this FBO is as large as the atlas, so it's a huge amount of memory. Correct me if I'm wrong, but I think if I use GL_DEPTH_COMPONENT32F as a format I'll reduce memory used by 2.

Thanks again for pointing me in the right direction.

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

  • Announcements

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • 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. 
      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!
    • 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.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
  • Popular Now