• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Maik Xhani

OpenGL
Opengl Multiple renderings, how to improve performance?

10 posts in this topic

Hello everybody I am working on an application that needs to render the scene from multiple points of view. I notice that if I render once, even if the frag shader is long and complicated (writing to multiple 3D textures) it runs at 65 FPS. As soon as I add another rendering pass before that (simply rendering to 2 targets, colour and normals+depth) the framerate drops to 40. If I add a shadowmap pass it drops even further to 25-30 FPS. What is the best way to cope with multiple renderings and still retain a high framerate?

 

This is what I have right now:

1 - a shader that computes the normal+depth and colors, 2 targets on the same FBO

2 - the same shader gets called again for the shadowmap (different uniform parameters) but renders to a different FBO target

3 - a shader that writes values on a 3D texture using imageStore, new FBO

4 - a last shader that performs ray marching through the 3D texture and, at the same time, reads from the 2 maps created before

if i just run step 3 and 4 i get 65 FPS, if i add the 2 steps above the performance drops and the only explanation I have is that I am doing something useless in the middle cause the shaders in 3 and 4 are way more complicated (1000+ lines)

Thank you 

0

Share this post


Link to post
Share on other sites

It's not strange that a severely un-optimized shader of 20 lines will get outperformed by a severely optimized shader of 100 lines (so to speak that is). Add the fact that you're using the same shader multiple times to render multiple viewpoints and your performance will go down the drain.

 

With that being said, we have no clue what your shaders look like so we can't really comment on anything if you're doing something wrong or not. It might be in the shaders, it might be in the way you are using the FBO, it might be something totally unrelated to either!

 

I'd suggest using a profiler to see where your bottleneck is, (double) check your shaders (1000+ lines for a single shader seems like a lot, but I don't know what you're aiming for) and check your code for silly mistakes.

 

But if you want help, post some code along with an explanation of what you're trying to achieve and I'm sure these lovely people are able to help you out!

Edited by Rld_
0

Share this post


Link to post
Share on other sites

I have Nsights installed in VS 13, would it work as a profiler for glsl? Btw the big shader is fine cause everything runs fast when i run it alone. The other one is slowing things down, Also, I have 5 FBOs with a total of 6 targets, maybe this is one of the things that is slowing down everything

0

Share this post


Link to post
Share on other sites

I never used Nsights before, but it seems like an option to rule some things out, but I'm not sure if it enables you to profile your shaders. A quick google already showed some options for you that might do the trick a bit better specifically for shaders.

0

Share this post


Link to post
Share on other sites

So I started doing some debugging with Nsight and I took a look at the events. This is what I saw:

 

I have numerous calls like this 

void glBindTexture(GLenum target = GL_TEXTURE_2D, GLuint texture = 15)	0x00010000	1539	0
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 1188, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 000354FC, GLint basevertex = 38051)	0x00010000	21038	22504
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 786, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0003678C, GLint basevertex = 38847)	0x00010000	17446	15872
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 786, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 000373D4, GLint basevertex = 39373)	0x00010000	16933	15292
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 786, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0003801C, GLint basevertex = 39899)	0x00010000	21552	14868
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 786, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 00038C64, GLint basevertex = 40425)	0x00010000	17960	14080
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 1188, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 000398AC, GLint basevertex = 40951)	0x00010000	16933	21740
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 1188, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0003AB3C, GLint basevertex = 41747)	0x00010000	16420	21856
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 786, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0003BDCC, GLint basevertex = 42543)	0x00010000	16933	15432
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 786, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0003CA14, GLint basevertex = 43069)	0x00010000	16933	15448
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 786, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0003D65C, GLint basevertex = 43595)	0x00010000	16420	14704
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 786, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0003E2A4, GLint basevertex = 44121)	0x00010000	16933	13788
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 1188, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0003EEEC, GLint basevertex = 44647)	0x00010000	16420	21668

and I guess I could turn those draw calls into a single call.

I then noticed this other thing:

void glBindTexture(GLenum target = GL_TEXTURE_2D, GLuint texture = 10)	0x00010000	1539	0
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 612, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0004017C, GLint basevertex = 45443)	0x00010000	21038	30748
void glBindTexture(GLenum target = GL_TEXTURE_2D, GLuint texture = 12)	0x00010000	1026	0
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 612, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 00040B0C, GLint basevertex = 45959)	0x00010000	20525	28388
void glBindTexture(GLenum target = GL_TEXTURE_2D, GLuint texture = 10)	0x00010000	1026	0
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 444, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0004149C, GLint basevertex = 46475)	0x00010000	20525	55416
void glBindTexture(GLenum target = GL_TEXTURE_2D, GLuint texture = 11)	0x00010000	1026	0
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 480, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 00041B8C, GLint basevertex = 46797)	0x00010000	20525	13716
void glBindTexture(GLenum target = GL_TEXTURE_2D, GLuint texture = 12)	0x00010000	1026	0
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 336, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0004230C, GLint basevertex = 47117)	0x00010000	20525	10060
void glBindTexture(GLenum target = GL_TEXTURE_2D, GLuint texture = 11)	0x00010000	1026	0
void glDrawElementsBaseVertex(GLenum mode = GL_TRIANGLES, GLsizei count = 480, GLenum type = GL_UNSIGNED_INT, GLvoid* indices = 0004284C, GLint basevertex = 47349)	0x00010000	20525	11676

Now in this one as you can notice I keep binding to the same 3 textures back and forth. Would it make sense to sort my elements based on texture object when I load the model, so that I can bind one texture and make all the draw calls and then go to the next?

0

Share this post


Link to post
Share on other sites

I'm not sure how expensive texture binding is, but it will probably increase performance by some if you keep it all together. Constantly (re)binding shaders is a costly thing, so you probably do want to have that sorted out.

 

Having less draw calls might also help.

 

You might also benefit from timing your instructions, see if something is taking up more time than it should. Most, if not all, profilers have an option to see your highest bottlenecks, but you can also time specific functions yourself if you want that.

0

Share this post


Link to post
Share on other sites

I notice that if I render once, even if the frag shader is long and complicated (writing to multiple 3D textures) it runs at 65 FPS1. As soon as I add another rendering pass before that (simply rendering to 2 targets, colour and normals+depth) the framerate drops to 40 FPS2. If I add a shadowmap pass it drops even further to 25-30 FPS3

That's 1=15.4ms, 2=25ms, 3=40 to 33ms per frame maximum from the CPU and GPU.

So your original pass is 15.4ms, your added pass is (25-15.4=) 9.6ms, and your shadowmap pass is (33-25= / 40-25=) 8ms to 15 ms.
 
Those all sound like feasible numbers... I don't know why you expect to be able to do more work without spending more milliseconds of GPU time wink.png tongue.png
 
You can use gl_ext_timer_query to measure how long different passes are taking on the GPU. e.g. insert a query before/after your shadowmap pass, and then next frame, retrieve the results of the query to find out what the duration of those commands on the GPU actually was.

0

Share this post


Link to post
Share on other sites

Actually I turned off vsync so that I get the actual FPS. So these are the actual results (voxelization is the expensive shader)

 

voxelization alone: 94 FPS

 

normal+depth and color pass alone: 240 FPS (I could improve this by using a g-buffer instead of 2 textures)

 

shadowmap alone: 135 FPS

 

normal+depth+color & shadowmap: 160 FPS (those 2 passes use the same shader)

 

second pass + shadowmap + voxelisation (in this order) : 67 FPS

 

The weird thing is that if I run the shadowmap pass alone it's slower than if i run it after th other pass, so it means that I am probabily wasting something. 

I will go on and try to optimize the voxelisation part. It's the cyril crassin method of rendering everything while using the geometry shader to project to the dominant axis and use the fragment shader to write to a 3d texture. Right now I am writing to the 3d Tex by using imageStore even though that doesn't seem the bottleneck of the shader.

 

If I use gl_ext_timer_query i get those results

 

normal+depth & color : 10,336,416 ns

shadowmap: 5,412,064 ns

voxelise: 55,344,416 ns

which should run at 14 fps...

 

all I did was

glBeginQuery(GL_TIME_ELAPSED_EXT, queries[0]);
firstPass();
glEndQuery(GL_TIME_ELAPSED_EXT);
glBeginQuery(GL_TIME_ELAPSED_EXT, queries[1]);
ShadowMapPass();
glEndQuery(GL_TIME_ELAPSED_EXT);
glDisable(GL_DEPTH_TEST);
glDisable(GL_CULL_FACE);
glBeginQuery(GL_TIME_ELAPSED_EXT, queries[2]);
Voxelize(false);
glEndQuery(GL_TIME_ELAPSED_EXT);

while (!available) {
	glGetQueryObjectiv(queries[4 - 1], GL_QUERY_RESULT_AVAILABLE, &available);
}
for (int i = 0; i < 3; i++) {
  // See how much time the rendering of object i took in nanoseconds.
  glGetQueryObjectui64vEXT(queries[i], GL_QUERY_RESULT, &timeElapsed);
}

I assure that the fps count above is correct because it is the same one that is displayed by NSight

0

Share this post


Link to post
Share on other sites

As demonstrated by Hodgman above: Using a non-linear measure like FPS (which is in fact reciprocal) is meaningless for quantitative assessment of relative performance. 

 

However, in your query code, IMHO this line

glGetQueryObjectiv(queries[4 - 1], GL_QUERY_RESULT_AVAILABLE, &available);

should read so

glGetQueryObjectiv(queries[3 - 1], GL_QUERY_RESULT_AVAILABLE, &available);

because you want to wait for queries[2] to be ready, not for (the not existing) queries[3].

Edited by haegarr
0

Share this post


Link to post
Share on other sites

sorry, that was my typo, I had an extra query before. Still the results are the same I posted

0

Share this post


Link to post
Share on other sites

I also tried this: i put a glFinish() at the end so that all the commands in the queue would be executed at that point. This is what shows up in the debugger

 

1 void glFinish() 0x00010000 1772914 0
2 void glClear(GLbitfield mask = GL_DEPTH_BUFFER_BIT) 0x00010000 7749507 0

 

glClear is taking 7 ms of CPU time?

 

If i run other stuff before it it takes even 12ms. Also I have 2 more glClear and they both take this long. Is this normal?

0

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  
Followers 0

  • Similar Content

    • By Toastmastern
      So it's been a while since I took a break from my whole creating a planet in DX11. Last time around I got stuck on fixing a nice LOD.
      A week back or so I got help to find this:
      https://github.com/sp4cerat/Planet-LOD
      In general this is what I'm trying to recreate in DX11, he that made that planet LOD uses OpenGL but that is a minor issue and something I can solve. But I have a question regarding the code
      He gets the position using this row
      vec4d pos = b.var.vec4d["position"]; Which is then used further down when he sends the variable "center" into the drawing function:
      if (pos.len() < 1) pos.norm(); world::draw(vec3d(pos.x, pos.y, pos.z));  
      Inside the draw function this happens:
      draw_recursive(p3[0], p3[1], p3[2], center); Basically the 3 vertices of the triangle and the center of details that he sent as a parameter earlier: vec3d(pos.x, pos.y, pos.z)
      Now onto my real question, he does vec3d edge_center[3] = { (p1 + p2) / 2, (p2 + p3) / 2, (p3 + p1) / 2 }; to get the edge center of each edge, nothing weird there.
      But this is used later on with:
      vec3d d = center + edge_center[i]; edge_test[i] = d.len() > ratio_size; edge_test is then used to evaluate if there should be a triangle drawn or if it should be split up into 3 new triangles instead. Why is it working for him? shouldn't it be like center - edge_center or something like that? Why adding them togheter? I asume here that the center is the center of details for the LOD. the position of the camera if stood on the ground of the planet and not up int he air like it is now.

      Full code can be seen here:
      https://github.com/sp4cerat/Planet-LOD/blob/master/src.simple/Main.cpp
      If anyone would like to take a look and try to help me understand this code I would love this person. I'm running out of ideas on how to solve this in my own head, most likely twisted it one time to many up in my head
      Thanks in advance
      Toastmastern
       
       
    • By fllwr0491
      I googled around but are unable to find source code or details of implementation.
      What keywords should I search for this topic?
      Things I would like to know:
      A. How to ensure that partially covered pixels are rasterized?
         Apparently by expanding each triangle by 1 pixel or so, rasterization problem is almost solved.
         But it will result in an unindexable triangle list without tons of overlaps. Will it incur a large performance penalty?
      B. A-buffer like bitmask needs a read-modiry-write operation.
         How to ensure proper synchronizations in GLSL?
         GLSL seems to only allow int32 atomics on image.
      C. Is there some simple ways to estimate coverage on-the-fly?
         In case I am to draw 2D shapes onto an exisitng target:
         1. A multi-pass whatever-buffer seems overkill.
         2. Multisampling could cost a lot memory though all I need is better coverage.
            Besides, I have to blit twice, if draw target is not multisampled.
       
    • By mapra99
      Hello

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

      Thanks!
    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
  • Popular Now