Skip to content

Soak at full scale: text vs bigint ids, 10M nodes / 100M edges (M10) - #62

Merged
wfaithfull merged 2 commits into
mainfrom
m10-soak-10m
Oct 24, 2026
Merged

wfaithfull merged 2 commits into
mainfrom
m10-soak-10m

Conversation

@wfaithfull

Copy link
Copy Markdown
Contributor

Case a at 10M nodes / 100M edges with --ids text and --ids bigint on the same machine, every stage included (recursive CTE baseline, second version with diff/distance, the library, louvain and leiden).

  • bench/results/soak/a-text-m10.json, a-m10.json and the README provenance.
  • DESIGN.md §12: the full-scale table replaces the half-scale "still to do", and explains why components and minimum_spanning_forest peak higher with text (every row's text datum is built in the SRF's multi-call context, about 72 bytes per id), with the fix described (return rows lazily) but not implemented.

Text costs 1.0–1.4× on most stages, about 2× on bfs and components, and 4.6× on similarity. Targets missed: reachable_set (13M / 19M edges/s against 50M), bfs vs the CTE (5.2× / 10.5× against 20×), and text components (10.6 s against 10 s).


Generated by Claude Code

Case a at 10M nodes and 100M edges with IRIs and with bigint ids, every
stage included, on an otherwise idle machine.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Rxfe2L3iVjSwSBPdUu1Ke
Replaces the half-scale paragraph's 'still to do' with the 10M-node run
beside its bigint pair, and explains the components and
minimum_spanning_forest peaks: every row's text datum is built up front
in the call's multi-call memory context, 72 bytes an id. Describes the
lazy-rows fix without building it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Rxfe2L3iVjSwSBPdUu1Ke
@wfaithfull
wfaithfull merged commit 37ab2a1 into main Oct 24, 2026
17 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.

2 participants