Skip to content

perf(logging): add guarded exec_mx lock-elision research - #139

Merged
LimiNode merged 3 commits into
mainfrom
perf/exec-mx-research
Sep 19, 2026
Merged

LimiNode merged 3 commits into
mainfrom
perf/exec-mx-research

Conversation

@LimiNode

Copy link
Copy Markdown
Owner

Summary\n- add explicit formatter/backend concurrency capability hooks (default false)\n- elide per-strategy exec_mx only when both capabilities opt in; retain serialized fallback\n- add fallback/opt-in regression tests and a 1/4/16/32 producer A/B benchmark\n- document the lifecycle contract in ADR 0006 and benchmark guidance\n\nThe benchmark is intentionally machine-specific research. Built-in backends remain serialized until their complete lifecycle contracts are audited.

Add explicit formatter and backend capability hooks with a serialized fallback so Logger can elide exec_mx only for implementations that document complete concurrent lifecycle safety. Cover the opt-in and fallback paths with deterministic tests and a 1/4/16/32 producer research benchmark, and document the contract in ADR 0006.
Replace make_unique in the capability regression test with explicit unique_ptr construction so the Linux C++11 matrix compiles with GCC.
@LimiNode
LimiNode force-pushed the perf/exec-mx-research branch from de588d1 to d94a69c Compare September 19, 2026 17:31
Require opted-in backends to make clear_logs safe alongside dispatch and lifecycle operations, matching the Logger paths that can run concurrently without exec_mx.
@LimiNode
LimiNode merged commit addb1d7 into main Sep 19, 2026
16 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