Measuring performance impact of tracing a system under load
Date: Mon, 18 Oct 2021 21:32:12 UTC
Hello everyone, I would like to measure the overhead / performance impact that of tracing with DTrace has on a system under load. I'm looking for the right way to do it. Obviously, I should not be using DTrace to measure that in this situation. I could use other stats(7) tools but it does not seem. Measuring the impact indirectly sounds like a good idea (e.g., by looking at the throughput between two machines in a test lab as they transfer bytes from A to B in two scenarios: with active tracing and without). Are there any other options? Do you have any insights to share regarding measuring DTrace overhead? I'd be grateful for all suggestions and pointers. Best, Mateusz Piotrowski