Repository navigation
Bump JasperFx to 2.22.0 — daemon connection governors (jasperfx#494–#496) - #3336
Merged
Merged
Conversation
#494-#496) JasperFx 2.22.0 bounds the async daemon's database connection footprint per database: MaxConcurrentEventLoadsPerDatabase (event-load throttle) and MaxConcurrentBatchWritesPerDatabase (projection batch-write governor), both default 4 and on by default, plus a bounded CrossTenantRebuild default. Measured at 200 per-tenant agents on one database: peak connections drop from 47-99 to a deterministic 12-14 with unchanged throughput and catch-up (epic #486 WS2+WS3; numbers on #494). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 9, 2026
Merged
This was referenced Jul 27, 2026
Closed
This was referenced Aug 3, 2026
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.
Part of epic #486 (WS2 + WS3); the marten twin is marten#4877. Consumes JasperFx 2.22.0, which bounds the async daemon's database connection footprint per database — on by default, no configuration required:
MaxConcurrentEventLoadsPerDatabase(default 4) — event-load throttle (MapWolverineEndpoints authorization? #495)MaxConcurrentBatchWritesPerDatabase(default 4) — projection batch-write governor (Programmatic way to delete existing nodes #496)CrossTenantRebuild.RebuildEverywhereAsyncnow defaultsmaxParallelismto 4 (was unbounded)This directly benefits Wolverine-managed event-subscription distribution under per-tenant partitioning: each node's daemon now holds O(databases) connections instead of O(assigned tenant agents). Measured at 200 per-tenant agents on one database: peak connections drop from 47–99 (racy) to a deterministic 12–14 with unchanged throughput and 100/100 tenant catch-up (record on #494).
Verified locally against the published packages: full
wolverine.slnxRelease build +MartenTests.Distribution31/31 (net9.0).🤖 Generated with Claude Code