Skip to content

note the post-thread-safety grpc benchmark bump in performance.md#434

Open
kacy wants to merge 1 commit into
mainfrom
docs/bench-rerun-threadsafety
Open

note the post-thread-safety grpc benchmark bump in performance.md#434
kacy wants to merge 1 commit into
mainfrom
docs/bench-rerun-threadsafety

Conversation

@kacy

@kacy kacy commented Jul 17, 2026

Copy link
Copy Markdown
Owner

summary

re-ran the full benchmark suite after the thread-safety sweep (#430-#433). the compute benchmarks (std_pipeline, catalog_workload, event_ledger, cyclic_graph) are unchanged within the box's noise — those paths don't touch tls/binary/grpc. the grpc benchmark improved: moving std.binary's reader off shared global maps into struct fields (#430) dropped a global-map access per frame parse, so a re-measurement put pith at ~3040 calls/sec sequential 16 B (matching tonic) and ~6300 8-concurrent (~2x scaling), while making the connection pool safe under real parallelism (it previously raced the global maps and crashed).

what was tested

ran grpc (pith/go/rust sweep), std_pipeline, catalog_workload, event_ledger (pith/go/rust/zig), cyclic_graph — all against the current build. docs-only change; the grpc numbers are the notable delta.

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