Reduce benchmark link counts to prevent CI timeout #18
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.
Summary
Fixes #17 - Benchmark is executing too long
The CI benchmark was timing out after 6+ hours because the number of links being created was too high for PostgreSQL operations.
Root Cause Analysis
CI Configuration (main branch):
BENCHMARK_LINKS: 1000 links per operationBENCHMARK_BACKGROUND_LINKS: 100,000 background links per iterationCriterion Warning: "Unable to complete 100 samples in 5.0s. You may wish to increase target time to 15547.2s"
Why PostgreSQL is slow: Network I/O + disk I/O for each operation, compared to in-memory Doublets operations
Changes Made
BENCHMARK_LINKS(main)BENCHMARK_BACKGROUND_LINKS(main)Expected Impact
Files Changed
.github/workflows/rust.yml- Reduced CI benchmark parametersrust/src/lib.rs- Updated default values and documentation🤖 Generated with Claude Code