Closed FlorianVeaux closed 2 days ago
Run ID: fb63d419-a0f0-41b0-a160-fe088e4d5e69 Metrics dashboard Target profiles
Baseline: 8779d4aae297b22e3bef8981a44665943bae895a Comparison: 3e3c1e4f6f5d81c1c2d2f9623117a64a325f033b
Performance changes are noted in the perf column of each table:
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
@FlorianVeaux would you mind pulling in the latest changes from the fork? I tested again and my calculation was slightly off.
It's unlikely we'd hit the issue ourselves, but it appears that the buffer needs to be large enough to hold:
p.Size + (ipv4.HeaderLen+8)*2
. Even though net
doesn't give us the original IP header, the underlying buffer needs to be large enough to hold it
/merge
:steam_locomotive: MergeQueue: pull request added to the queue
The median merge time in main
is 25m.
Use /merge -c
to cancel this operation!
Internal context: https://datadoghq.atlassian.net/wiki/spaces/II/pages/3860988548/BUG+Windows+Ping+Buffer+Issue
A windows-only issue affects the pro-bing library, described in this issue: https://github.com/prometheus-community/pro-bing/issues/34
With this PR, we replace the pro-bing version to the one from a personal fork from @ken-schneider. Once the PR is merged upstream, we'll move back to the main branch.