Skip to content

concurrency: add round-trip latency percentile test for USPSCQueue#2653

Open
pjsutar wants to merge 1 commit into
facebook:mainfrom
pjsutar:feat/spsc-latency-benchmarks
Open

concurrency: add round-trip latency percentile test for USPSCQueue#2653
pjsutar wants to merge 1 commit into
facebook:mainfrom
pjsutar:feat/spsc-latency-benchmarks

Conversation

@pjsutar
Copy link
Copy Markdown

@pjsutar pjsutar commented May 22, 2026

Motivation: the existing bench test measures throughput (ops/sec) but omits tail latency. In real-time pipelines such as sensor DAQ systems and market data handlers, p99/p999 latency is the binding constraint.

Changes:

  • Add UnboundedQueue.RoundTripLatencyPercentiles test
  • Producer enqueues send timestamp as payload; consumer echoes it back
  • Measures p50/p95/p99/p999 round-trip latency in nanoseconds
  • Uses steady_clock (monotonic) to avoid wall-clock skew
  • Includes 1000-iteration warmup before recording measurements
  • Sanity assertions verify positive and monotonically ordered percentiles

Sample output (WSL2, Intel Core i7, gcc 13):
p50=309ns p95=413ns p99=516ns p999=1134ns

Tested: gcc 13, Ubuntu 22.04 LTS (WSL2), x86_64

Motivation: the existing bench test measures throughput (ops/sec) but
omits tail latency. In real-time pipelines such as sensor DAQ systems
and market data handlers, p99/p999 latency is the binding constraint.

Changes:
- Add UnboundedQueue.RoundTripLatencyPercentiles test
- Producer enqueues send timestamp as payload; consumer echoes it back
- Measures p50/p95/p99/p999 round-trip latency in nanoseconds
- Uses steady_clock (monotonic) to avoid wall-clock skew
- Includes 1000-iteration warmup before recording measurements
- Sanity assertions verify positive and monotonically ordered percentiles

Sample output (WSL2, Intel Core i7, gcc 13):
  p50=309ns  p95=413ns  p99=516ns  p999=1134ns

Tested: gcc 13, Ubuntu 22.04 LTS (WSL2), x86_64
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 22, 2026

Hi @pjsutar!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla meta-cla Bot added the CLA Signed label May 22, 2026
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 22, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant