Repository navigation
Conversation
…urements Use an independent Go client/origin, per-process CPU affinity, validated response payloads, three shuffled rounds, explicit fresh/reused HTTP1 cases, HTTP2 TLS/cleartext, CONNECT throughput and held-tunnel resources. Build and test d500d25 unchanged against C Tinyproxy 1.11.3. Keep workflow read-only and preserve raw results without test private keys.
…xperiment Keep main and baseline source unchanged. Compare accepted/outgoing TCP NODELAY as a separate tested binary; retain its patch and binary hash. Capture startup errors and distinguish logical-CPU affinity from physical core isolation. Do not count the failed C harness setup as a proxy result.
C file-path directives require quotes; no PID or log file is needed for these foreground test processes. Validate C, Rust, and experimental plain/TLS modes through the independent client before timed rounds.
A process can disappear or temporarily deny fd inspection after poll() reports it alive. Skip that sample on OSError; network successes/errors remain independently recorded by the load generator.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a local-only independent Go load generator/origin, a bounded Linux benchmark harness, a read-only Actions workflow, and the completed measured report at
docs/benchmarks/2026-09-19.md.This PR changes benchmark tooling and documentation only. Runtime source and
mainare unchanged. A TCP_NODELAY experiment is built only in an isolated checkout and recorded as a separate binary/diff, not silently applied to the baseline.Completed verification
Benchmark run: https://github.com/Ray0907/tinyproxy-rust/actions/runs/35413653419
Runtime baseline:
d500d2510475daafa8269e09caea6d2043c26aa5; C Tinyproxy 1.11.3, release checksum verified. Benchmark harness in that run:93353a2dcdec2ecf0d9dae5e373611b99a06e6e3.Findings, not blanket claims
Limits and review notes
Short closed-loop loopback measurements on a shared Ubuntu CI VM, 1 s warmup + 4 s measurement per round. Separate logical CPU affinities are not physical-core isolation: proxy and origin share an SMT core in the recorded topology. Numbers are medians of per-round values. Fresh/reused H1 and cleartext/TLS cases are labeled separately. No WAN, full conformance, DoS, long-soak or universal performance superiority claim.
Earlier attempts failed due harness configuration/procfs-monitor errors; those incomplete runs are excluded and documented. The NODELAY result supports a TCP buffering explanation but no packet capture was taken. Follow-up runtime tuning should separately evaluate latency, relay buffers and bulk-transfer CPU costs.
No merge or release is performed by this PR.