Skip to content

Infinity density harness — publishable same-host 8G history fit (~29%) - #1443

Merged
cursor[bot] merged 19 commits into
mainfrom
cursor/infinity-on-pi-reproduce-f425
Oct 31, 2026
Merged

cursor[bot] merged 19 commits into
mainfrom
cursor/infinity-on-pi-reproduce-f425

Conversation

@danielsmithdevelopment

@danielsmithdevelopment danielsmithdevelopment commented Oct 29, 2026 •

Copy link
Copy Markdown
Owner

Summary

publishable: true with host disclosed. Live marketing board: /benchmarks#program-density (this PR). Ready for Infinity / Shadaj review before any “denser than” promotion.

Claim scope (important)

With matched 20-turn histories under the same 8 GiB cap: ClawQL’s resident history store fits ~29% more agents (100k vs 77.5k). This is a memory / history-storage result — not “the full ClawQL runtime runs 29% more agents.” Infinity’s arm is full agent_scale; ClawQL’s is the matched-shape history harness. Outreach draft: docs/benchmarks/program-density/infinity-on-pi/outreach-shadaj-draft.md.

Headline

Arm Latency-gated N RSS/N
Infinity agent_scale 77 500 ~105.3 KiB
ClawQL matched-shape resident 100 000 ~78.8 KiB

Fit quality: within-system ratios (Infinity p99 1.04×, ClawQL 1.69×). Criteria frozen in evidence as frozenCriteria.

/benchmarks page (this update)

  • New #program-density section: chips, fit table, latency ratios, reclaim, open-host slopes, offloaded trade-off, honesty notes, artifact links
  • Hero callout + jump link (history density ~29%)
  • Dominance roadmap Infinity row + docs index / STATUS pointers
  • Cross-links from gateway + governance boards

Hero History density callout
Program density fit table
benchmarks-program-density-demo.mp4

Host

Intel(R) Xeon(R) Processor, family 6 / model 207 / stepping 2 @ 2400 MHz, 4 vCPU, KVM — likely Emerald Rapids (guest cannot confirm SKU). DMI product_name unavailable.

Ask for Shadaj’s team

Allocator analog to --max-old-space-size=8192? Fuller ClawQL arm if they want runtime parity?

Test plan

  • Claim scoped to history-memory density
  • frozenCriteria in evidence
  • Likely Emerald Rapids noted
  • Outreach draft with candor
  • /benchmarks#program-density section + hero jump + dominance/docs pointers
  • apps/www static build + local serve smoke (section HTML + UI screenshots/demo)
  • CI green
  • Shadaj peer review before promotion

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

cursoragent and others added 2 commits October 29, 2026 20:05
Pin hydro-project/infinity@341f6c2 and rerun their agent_scale example
(AGENTS=10000 TURNS=20). Idle RSS ~103.1 KiB/agent matches the public
~100 KB claim on this x86 host — Pi 5 hardware measurement still next.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Add fair-v2 parked ClawQL column next to reproduced Infinity agent_scale on
this cloud host. Pi 5 hardware stays deferred; report adjacent RSS/disk columns
without win copy.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
@cursor cursor Bot changed the title Infinity-on-Pi step 1: reproduce agent_scale ~103 KiB/agent Infinity same-host density vs ClawQL (Pi hardware deferred) Oct 29, 2026
Close the four like-for-like gaps on this KVM cloud-agent host
(publishable:false): Infinity-matched byte parity, runtime-driven turns,
RSS slope floors (3-rep fresh processes), resident+offloaded arms, and
cgroup memory.max=8G ramps. Pi hardware remains a deferred column.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
@cursor cursor Bot changed the title Infinity same-host density vs ClawQL (Pi hardware deferred) Infinity density harness v2 (parity, slope, 8G) — Pi deferred Oct 29, 2026
Shared scripted strings undercounted ClawQL resident RSS (52 KiB < 63 KiB
history; 197k × 52 KiB could not fit 8G). Embed unique tags in both Infinity
and ClawQL fixtures, require resident slope ≥ serialized history, and remeasure
slopes + 8G cgroup ramps (publishable:false).

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
@cursor cursor Bot changed the title Infinity density harness v2 (parity, slope, 8G) — Pi deferred Infinity density harness v2 — unique histories + 8G (Pi deferred) Oct 29, 2026
memory.swap.max=0 on 8G runs (peak verified 0 — not swap). Force multi-pass
gc() before RSS samples. Add lastFit×slope≤cap integrity plus harness-floor
cross-check so ClawQL’s ~100 KiB open-host slope cannot be jointly quoted with
102.5k@8G (use ramp RSS/N ~79 KiB for fit). Reframe offloaded as a trade-off
row next to Infinity serverless.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
@cursor cursor Bot changed the title Infinity density harness v2 — unique histories + 8G (Pi deferred) Infinity density harness — equal residents, honest 8G, offload trade-off Oct 29, 2026
cursoragent and others added 6 commits October 30, 2026 12:43
Add DensityConversationRuntime.wake, extend mincore/evict globs to dens_*.json,
and publish evidence-offloaded-tradeoff.json for the disk/page-cache/wake trade-off
row next to Infinity serverless (publishable:false on this KVM host).

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Measure per-turn latency at baseline vs lastFit under memory.max=8G for
ClawQL and Infinity. Both stay within 2× of baseline at lastFit. Lead with
measured agents-that-fit (102.5k vs 77.5k, ~32%) and RSS/N (~79 vs ~105 KiB).
Disclose --max-old-space-size=8192 and Infinity malloc_trim tuning question.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Same latency-gate rule both sides (headline ClawQL 100k, not unverified
102.5k). Restore baseline/lastFit p50/p99 latency table. Disclose forced
reclaim (gc / malloc_trim) on both. Flip publishable:true with host
disclosed — same standard as other ClawQL cloud boards.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
…line

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
@cursor cursor Bot changed the title Infinity density harness — equal residents, honest 8G, offload trade-off Infinity density harness — publishable same-host 8G fit (~29%) Oct 30, 2026
cursoragent and others added 2 commits October 30, 2026 17:42
Lead fit-quality with lastFit÷baseline ratios (Infinity p99 1.04×, ClawQL
1.69×) so absolute ms cannot be misread as a cross-system speed claim.
Record /proc/cpuinfo model+CPUID and note DMI product_name absent on this guest.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
…Rapids likely

Scope the 29% headline to matched-history storage under 8 GiB — not full
ClawQL runtime. Freeze gates in evidence.frozenCriteria. Note CPUID 6/207 is
likely Emerald Rapids. Add outreach draft for Shadaj's team with that candor.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
@cursor cursor Bot changed the title Infinity density harness — publishable same-host 8G fit (~29%) Infinity density harness — publishable same-host 8G history fit (~29%) Oct 30, 2026
github-actions Bot and others added 6 commits October 30, 2026 17:52
Add #program-density section (100k vs 77.5k, ~29%) with fit/latency/
reclaim/offload tables, hero jump, dominance Infinity row, and docs
pointers. Claim scoped to matched-history memory under 8 GiB.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Satisfy preserve-caught-error so CI Lint & format can pass before merge.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Clear new HIGH supply-chain findings blocking CI (CVE-2026-116689,
CVE-2026-118779 family). Drop obsolete node-forge ignores now that
a patched release is locked.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Clear remaining medium OSV findings (GHSA-g3hv-75wg-m249,
GHSA-3g3m-2fjr-6pw4) after Trivy already passed on the HIGH CVEs.

Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
@cursor
cursor Bot merged commit d684900 into main Oct 31, 2026
31 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