Graphics Reference
In-Depth Information
In this chapter, we walked through a lot of tips and tricks with regard to performance. As
is always recommended when dealing with performance issues, finish the code first. Do
not spend time optimizing the code for a “possible” bottleneck until that bottleneck is
confirmed.
It is also highly recommended to test potential bottlenecks and have recordable results.
Sometimes, a simple fps (frames per second) recording is sufficient to test the bottleneck.
With recordable results, we can confirm that any performance changes were positive
instead of being a no-op or, worse, having a negative impact.
