Repository navigation
docs: tuning guidance from the 1.0 load tests - #236
Merged
Merged
Conversation
wolf4ood
marked this pull request as ready for review
October 30, 2026 08:31
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.
What this PR changes/adds
Extends the Tuning page with what the 1.0 load tests showed (multi-tenant runtime, up to 100 participants,
negotiation + transfer at 40+ flows/s):
before the transaction), and adds the NATS workers to the pool sizing.
edc.did.resolver.cache.size/.expiry. The cache is shared by all hosted participants,and a miss is a synchronous HTTP fetch on the request thread. With 99 counter-parties the default of 50 entries
raised the median negotiation time from ~1 s to 11 s.
WebDidResolver.resolve.edc.policy.cel.expressions.cache.ttl.ms, and what it means for multi-replica setups.warning about JDK builds that don't detect it on kernels without cgroup v1 memory support (observed with Temurin
24.0.2).
Why it does that
Briefly state why the change was necessary.
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.