OpenGL Driver Monitor is a developer tool that has two purposes. It is:
An application that lets developers see how OpenGL works on a specific system and look at the capabilities of a driver
An advanced diagnostic tool that OpenGL driver developers and experts can use to track down thorny performance issues
Most OpenGL developers should not use the driver monitor application to analyze performance issues; they should instead use Shark and OpenGL Profiler.
You’ll want to read this document if you:
Develop applications that use OpenGL on OS X and you are curious as to how the GPU and CPU interact
Want to look at the capabilities of a particular OpenGL driver
Are an OpenGL driver developer who needs to investigate a driver bug
Are an advanced OpenGL developer or consultant trying to track down a performance issue that you’ve been unable to analyze using Shark and OpenGL Profiler
Organization of This Document
This document is organized into the following chapters:
“Using OpenGL Driver Monitor” describes how to set preferences, collect real-time parameter values locally or remotely, and view renderer information.
“Identifying and Solving Performance Issues” provides strategies for using OpenGL Driver Monitor to analyze performance issues.
“OpenGL Driver Monitor Parameters” describes, by symbolic and descriptive names, the parameters that you can monitor.
These documents contain information that can help you analyze and optimize your OpenGL code: