I’m comparing the simpleGL project using VBO (Vertex Buffer Object) against Vertex Array (copying the mesh from the host to device, calculating the new mesh and copy back from device to host), I see great timings for VBO with a big mesh… the problems is why the VA is more efficient when the mesh is small… I run 256 x 256 vertex and VA takes less than 1ms and VBO takes about 16ms, I see that the cudaGLMapBufferObject() and cudaGLUnmapBufferObject() has some issues with timing… does anybody has something to say about this? thanks.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| MapBufferObject/UnmapBufferObject timings problem | 0 | 3208 | October 20, 2008 | |
| VBOs don't improve performance? What am I doing wrong? | 0 | 1529 | July 2, 2008 | |
| cudaGLMapBufferObject (and unmap) performance These calls take way too long | 47 | 76562 | February 14, 2010 | |
| Cuda OpenGL Interoperability efficiency problem | 4 | 1770 | August 28, 2011 | |
| CUDA access to VBO slow? | 0 | 1362 | February 17, 2012 | |
| A problem of CUDA & OpenGL interoperation | 4 | 3979 | May 17, 2009 | |
| MapBufferObject and UnmapBufferObject timings | 6 | 2696 | October 21, 2008 | |
| cudaMalloc vs mapped VBO | 2 | 3981 | March 2, 2007 | |
| cudaGLMapBufferObject on 2.3 Is still Slow? | 2 | 1363 | September 7, 2009 | |
| device->host->device copy vs cudaGLMapBufferObject 6vs9ms, shouldn't mapping be way faster | 0 | 4838 | July 12, 2007 |