Increase revolutions of context propagation benchmarks

[PROFeNoM]

Description

These benchmarks are flaky, particularly because of their short execution time, which is too short for microtime's precision. Increasing revolutions may address this issue.

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-01-12 09:03:13

Comparing candidate commit 5237b4c in PR branch alex/bench/flaky-revs with baseline commit b032b1e in branch master.

Found 6 performance improvements and 1 performance regressions! Performance is the same for 34 metrics, 49 unstable metrics.

scenario:ContextPropagationBench/benchExtractHeaders128Bit

• 🟩 execution_time [-6.537µs; -6.215µs] or [-89.959%; -85.527%]

scenario:ContextPropagationBench/benchExtractHeaders64Bit

• 🟩 execution_time [-12.627µs; -11.548µs] or [-94.233%; -86.178%]

scenario:ContextPropagationBench/benchExtractTraceContext128Bit

• 🟩 execution_time [-12.550µs; -11.993µs] or [-85.375%; -81.585%]

scenario:ContextPropagationBench/benchExtractTraceContext64Bit

• 🟩 execution_time [-6.572µs; -6.183µs] or [-90.654%; -85.277%]

scenario:ContextPropagationBench/benchInject128Bit

• 🟩 execution_time [-12.708µs; -12.315µs] or [-85.287%; -82.652%]

scenario:ContextPropagationBench/benchInject64Bit

• 🟩 execution_time [-31.652µs; -30.036µs] or [-82.643%; -78.422%]

scenario:PHPRedisBench/benchRedisBaseline

• 🟥 execution_time [+88.984µs; +326.630µs] or [+2.935%; +10.775%]