diff options
| author | Bartosz Taudul <wolf.pld@gmail.com> | 2017-10-03 16:37:35 +0300 |
|---|---|---|
| committer | Bartosz Taudul <wolf.pld@gmail.com> | 2017-10-03 16:37:35 +0300 |
| commit | fee676674d9167725605aebd3c292a6a78e2e68a (patch) | |
| tree | f48c33e9f5e46b75237de0f0e91e6cf4a76cc4c9 /README.md | |
| parent | 2fb4c47491758ec877d7be86e7d86fd75dc2d9e2 (diff) | |
Support for rdtscp on non-windows platforms.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -52,7 +52,7 @@ Alternatively, you may want to embed the server in your application, the same wh Tracy's time measurement precision is not infinite. It's only as good as the system-provided timers are. - On the embedded ARM-based systems you can expect to have something around 1 µs time resolution. -- On x86 (currently only implemented on Windows) the time resolution depends on the hardware implementation of the RDTSCP instruction and typically is in the low nanoseconds. This may vary from one micro-architecture to another and requires a fairly modern (Sandy Bridge) processor for reliable results. +- On x86 the time resolution depends on the hardware implementation of the RDTSCP instruction and typically is in the low nanoseconds. This may vary from one micro-architecture to another and requires a fairly modern (Sandy Bridge) processor for reliable results. While the data collection is very lightweight, it is not completely free. Each recorded zone event has a cost, which tracy tries to calculate and display on the timeline view, as a red zone. Note that this is an *approximation* of the real cost, which ignores many important factors. For example, you can't determine the impact of cache effects. The CPU frequency may be reduced in some situations, which will increase the recorded time, but the displayed profiler cost will not compensate for that. |