next up previous contents
Next: Application bottlenecks. Up: 16.1 What Is Pipeline Previous: Three-Stage Model of the

16.1.2 Finding Bottlenecks in Your Application

The basic strategy for isolating bottlenecks is to measure the time it takes to execute a program (or part of a program) and then change the code in ways that don't alter its performance (except by adding or subtracting work at a single point in the graphics pipeline). If changing the amount of work at a given stage of the pipeline does not alter performance appreciably, that stage is not the bottleneck. If there is a noticeable difference in performance, you've found a bottleneck.





David Blythe
Thu Jul 17 21:24:28 PDT 1997