4 ms·
On application side I recommend using an instrumenting profiler that will let you know down to sub-microseconds what the code is doing. Tracy is a good choice (
by Torkel 6y ago
On application side I recommend using an instrumenting profiler that will let you know down to sub-microseconds what the code is doing. Tracy is a good choice (https://github.com/wolfpld/tracy https://github.com/wolfpld/tracy) but there are others, e.g. Telemetry.
- jeffbee 6y agoI can't tell what Tracy does because the documentation is so poor. Check out XRay for an older but still actively developed function tracing tool that generates traces which can be viewed in the Chrome trace viewer. https://llvm.org/docs/XRayExample.html#debugging-with-xray https://llvm.org/docs/XRayExample.html#debugging-with-xray
- Torkel 6y agoDid you see the pdf manual? I would actually have preferred something online for docs, but there is not a lack of documentation for Tracy.
- ezekiel68 6y agoSo, I just spent 2 hours checking this (tracy) out and I must say I am impressed. Here's a good video [1] from two years ago that shows its capabilities, and it's had 5 releases since then (check his YouTube channel for more recent vids of new features added). [1] https://www.youtube.com/watch?v=fB5B46lbapc https://www.youtube.com/watch?v=fB5B46lbapc ps I once had a different username, but don't login often and forgot my pwd (with no email addr on file) :( I've been on HN for years. Not affiliated in any way with the tracy project or its author.