Lines Matching full:performance

49     performance counters to the OpenGL applications. Performance counters may
62       case the result of performance counter usually represents the number of
65     This extension specifies universal API to manage performance counters on
66     different Intel hardware platforms. Performance counters are grouped
70     It is assumed that performance counters are started and ended on any
73     A set of performance counters is represented by a unique query type. Each
75     (sets of performance counters) are supported by the Intel hardware. However
76     each Intel hardware generation supports different sets of performance
80     Intel OGL Performance Counters Specification issued per each new hardware
162     4.4 Performance Queries (for OpenGL 4.4)
163     2.18 Performance Queries (for OpenGL ES 3.0.2)
165     Hardware and software performance counters can be used to obtain
166     information about GPU activity. Performance counters are grouped into query
176     returns the identifier of the first performance query type that is
179     performance queries, then the value of 0 is returned and INVALID_OPERATION
187     This function returns the integer identifier of the next performance query
190     query available the value of 0 is returned. If the specified performance
195     Each performance query type has a name and a unique identifier. The query
211     The function returns information about the performance query specified with
219     -  number of performance counters in the query output structure in
241     Performance counters that belong to the same query type have unique
242     ids. Performance counter ids values start with 1. Performance counter id 0
243     is reserved as an invalid counter. Information about performance counters
253     performance counter that is an element of the performance query. The
293     A single instance of the performance query of a given type can be created
310     created performance query instance, an INVALID_VALUE error is generated.
319     created performance query instance, an INVALID_VALUE error is
326     Because the API and GPU are asynchronous, the start of performance counters
329     of performance counters will start before any draw calls specified in the
332     Collecting performance counters may be stopped by a function:
338     by BeginPerfQueryINTEL().  If a performance query is not currently started,
407     Generally there are two approaches of measuring performance with Intel OGL
408     Performance Queries, such as:
410     - Per draw call measurements - performance counters can be used to assess
414     - Per 3D scene measurements - performance counters can be used to assess
423        independently. It is recommended to measure the GPU performance
429        The usage model assumes that one performance query instance measures a
433        - For a longer scope of performance query the probability of 3D hardware
479        of performance counters expressed in hardware clocks to be inaccurate.