Conversation
Benchmark results for collatzParameters
SummaryFound 0 performance improvements and 0 performance regressions! Performance is the same for 1 metrics, 0 unstable metrics. See unchanged results
|
Benchmark results for BadBoggleSolver_runParameters
SummaryFound 0 performance improvements and 0 performance regressions! Performance is the same for 1 metrics, 0 unstable metrics. See unchanged results
|
| } | ||
| PerfClock::init(static_cast<PerfClockSource>(rb.perf_clock_source)); | ||
| } else { | ||
| PerfClock::init(PerfClockSource::kClockMonotonic); |
There was a problem hiding this comment.
because monotonic is what the full host profiler would expect, and tsc logic is not available
There was a problem hiding this comment.
On otel profiler mode, PerfClock is not used to timestamp samples (since it's done on eBFP side), I had to initialize it because it's also used to determine when periodically check for newly loaded libraries.
There was a problem hiding this comment.
And indeed TSC calibration is done on ddprof side and is not available here.
|
ccc1c4d to
95c30f3
Compare
Just saw that, USDT probe seems to have a big impact on stack size in sanitized mode. |
95c30f3 to
3c0d453
Compare
3c0d453 to
3954635
Compare
|
I'm not sure if the crash is reproducible and a product of the PR (relaunching the CI) |
|
I agree on the TODO about a better description 😄 |
| auto stack_size = to_address(tl_state.stack_bounds.end()) - stack_base_ptr; | ||
|
|
||
| // stack will be saved in save_context, add some margin to account for call | ||
| // stack will be saved in save_context, add some ` to account for call |
There was a problem hiding this comment.
minor, comment was broken here
|
@nsavoire do you mind moving this to draft if we do not plan on merging soon ? |
What does this PR do?
Make
libdd_profiling.socompatible for use with otel profiler by creating a new mode that does not start ddprof and adding a USDT probe inside sampling path.(TODO) better description