title: When profiling, most of the time is spent in nvoglv64.dll. What should I deduce?
body: <p>I am profiling a C++ application with Intel VTune Amplifier. Most of the time seems to be spent in nvoglv64.dll more precisely in DrvPresentBuffers and/or KeSynchoronizeExecution. Note that I have a NVIDA GeoForce graphic card.</p>
  
  <p>I am new to the application I am profiling and looking for bottleneck and low hanging fruits of optimization. Since most of the time seems to be spent in this NVIDIA dll, I do not know how decode the profiling results.</p>
  
  <p>I would like to know where are those call from my application side in order to build a knowledge of my application. Can someone give me some hint to start : </p>
  
  <ul>
  <li>When exactly do an application call DrvPresentBuffers, what kind of call should I look at (on my application side)</li>
  <li>Where can I get more info about how to profile, understand and optimize applications where bottlenecks are in the graphic card dll's.</li>
  </ul>