20
edits
Performance:Probes: Difference between revisions
Jump to navigation
Jump to search
→Requirements: start
Stan Shebs (talk | contribs) (prior work) |
Stan Shebs (talk | contribs) (→Requirements: start) |
||
| Line 4: | Line 4: | ||
== Requirements == | == Requirements == | ||
Probes should be low impact when not in use. Ideally they would be zero impact when not in use, but this typically requires platform-specific and/or OS support. Impact needs to be minimal when in use. | |||
Probes should be able to be enabled and used in both debugging and optimized builds. They do not need to be available in production builds (although it is useful sometimes, we don't need it to be a requirement). | |||
Probing should be available on all supported platforms. It is allowable for the performance impact to be lower and the data quality to be better on some platforms. | |||
It should be possible to monitor entry and exit from individual functions. | |||
Probe timing data should be high resolution, to the microsecond level at least. | |||
== nsProbes == | == nsProbes == | ||