Repository navigation
Infinity density harness — publishable same-host 8G history fit (~29%) - #1443
Merged
Merged
Conversation
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>
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>
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>
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>
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>
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>
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>
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.
Summary
publishable: truewith 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
agent_scaleFit quality: within-system ratios (Infinity p99 1.04×, ClawQL 1.69×). Criteria frozen in evidence as
frozenCriteria./benchmarkspage (this update)#program-densitysection: chips, fit table, latency ratios, reclaim, open-host slopes, offloaded trade-off, honesty notes, artifact linkshistory density ~29%)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
frozenCriteriain evidence/benchmarks#program-densitysection + hero jump + dominance/docs pointersapps/wwwstatic build + local serve smoke (section HTML + UI screenshots/demo)To show artifacts inline, enable in settings.