You should really not randomly speculate when doing adversarial comparisons. Note: I am not a author of FunctionTrace. 1. You claim ~5% overhead [1] and it is

You should really not randomly speculate when doing adversarial comparisons. Note: I am not a author of FunctionTrace. 1. You claim ~5% overhead [1] and it is not useful for profiling tiny functions. They claim ~10% overhead when handling tiny functions and, who I believe to be the author of the package below, said it averages low single digit percents (i.e <5%) on normal non-worst cases. This is comparable or less overhead than you claim. 2. Sampling is so much worse than a full execution trace from a performance optimization and observability perspective it is ridiculous. Yes, a magnifying glass and a microscope are both okay for looking at ants, but only one is good for looking at cells. People prefer sampling because it was traditionally lower overhead, but for the same cost full tracing is so much better it is not even worth comparing, the result is patently obvious. 3. No “upload” is done. You are not sending data to them, everything is local. They are just opening the profiling data using Firefox to use it as a viewer like how you might open a PDF in Firefox. [1] https://www.sciagraph.com/docs/understanding/fil/ https://www.sciagraph.com/docs/understanding/fil/