Skip to content

perf(bench): add formatted public macro scenario - #136

Merged
LimiNode merged 3 commits into
mainfrom
perf/benchmark-follow-up
Sep 14, 2026
Merged

LimiNode merged 3 commits into
mainfrom
perf/benchmark-follow-up

Conversation

@LimiNode

Copy link
Copy Markdown
Owner

Summary

  • add a separate SimpleLogFormatter public LOGIT_INFO(...) benchmark alongside the passthrough record-construction scenario;
  • add a versioned benchmark fixture contract and runtime metadata line for compiler/toolchain/source commit/queue/flush settings;
  • run both public-macro scenarios in the Linux benchmark CI job;
  • mark the benchmark follow-up complete in the roadmap while keeping production exec_mx lock-elision as a separate research item.

Verification

  • local Release build passed for logit_public_macro_bench, logit_public_macro_formatted_bench, logit_hotpath_bench, logit_hotpath_bench_legacy, and logit_bench;
  • local smoke passed for passthrough and formatted public macro benchmarks, hot-path A/B, and filtered latency benchmark;
  • fixture JSON parses successfully;
  • git diff --check passed.

This PR does not change production logger synchronization or claim universal performance gains.

@LimiNode
LimiNode force-pushed the perf/benchmark-follow-up branch from 78caa7a to 8f042bf Compare September 13, 2026 22:49
Add a distinct SimpleLogFormatter benchmark alongside the passthrough public macro smoke. Record versioned fixture metadata for latency runs, keep the producer matrix explicit, and execute both public scenarios in CI without changing production logger locking.
Synchronize public-macro producers with a ready/start barrier and optional warmup, and share versioned metadata across benchmark targets. Require explicit build and hardware identity for comparable runs, update the fixture and methodology docs, and exercise metadata validation in CI benchmark smoke tests.
Require source commits for benchmark provenance without requiring them to match across before/after runs. Define the metadata_must_match fixture contract and document that comparable mode validates metadata completeness rather than canonical workload values.
@LimiNode
LimiNode force-pushed the perf/benchmark-follow-up branch from d8d60b3 to d85448e Compare September 14, 2026 16:25
@LimiNode
LimiNode merged commit baaf936 into main Sep 14, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant