Changes between Version 4 and Version 5 of GraphicsProfiling

Timestamp:

Jan 22, 2021, 1:13:29 PM (3 years ago)

Author:

Vladislav Belov

Comment:

--

GraphicsProfiling

@@ -4 +4 @@
 
 This page aims to give an overview of the various tools available for profiling graphics part of the game (i.e. measuring speed and resource usage), and some details on how to use them.
+
+== Frame profiling ==
+
+=== apitrace ===
+
+1. Install apitrace from https://apitrace.github.io/#download (analyzing scripts require Python 3)
+2. Capture a trace. Currently apitrace can't capture an interval, it starts capturing from the beginning. So it makes sense to repeat the needed frame as fast as possible using a window size as small as possible (a minute capture might use few GBs).
+{{{
+path/to/apitrace trace --api gl --output 0ad.trace path/to/pyrogenesis [pyrogenesis arguments...]
+}}}
+
+3. Analyze the capture.
+{{{
+path/to/apitrace replay --headless --pframe-times --pgpu --pcpu --ppd 0ad.trace > 0ad.trace.profiling.txt
+}}}
+  * {{{--pframe-times}}} record frames times, waiting for presentation to finish before starting next frame.
+  * {{{--pgpu}}} record GPU times for frames and draw calls.
+  * {{{--pcpu}}} record CPU times for frames and draw calls.
+  * {{{--ppd}}} record pixels drawn for each draw call.
+  * {{{--headless}}} don't show windows.
+
 
 == Graphics profiling and debugging tools ==