Publish: per-item timing and size logs, ETA for large sites, parallel checks and uploads #6
Labels
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rhelwig/DecentSite#6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Publishing speed is acceptable for a small site but won't scale. At today's per-item pace, a large site could take hours.
Seen on 2026-10-10: ronhelwig.com (11 pages) took a long time to publish. Auth runs about 36 proof reads of inspection before every write, all of it serially.
Wanted:
Related: only-changed versioning and continue-on-fail.
Follow-up notes: https://git.ronhelwig.com/rhelwig/DecentSite/src/branch/main/docs/PUBLISH-FOLLOWUPS-2026-10-10.md
Started on branch
feat/publish-timing-logs(c1fd3ee, not merged yet).Done so far: the Auth engine's
executeReleasenow recordstimingfor each item:bytes(size of the reviewed properties),totalMs, andstagesMsfor checking, signing, broadcasting and verifying. It also records a total for the whole run.onStepincludes the timing with each outcome. The timing data contains no SDK text and no record contents. New test added; 167/167 pass.Next: keep timing in Auth's Publication history and add an export. Log Admin's IPFS upload time and bytes per blob. Then build the ETA from past runs. Then try the speed experiments: one inspection per run, parallel proof reads, and concurrent uploads. The plan, including design notes for #5, is in
docs/IMPLEMENTATION-PLAN.mdon that branch.Progress update. PR #9 (
feat/publish-timing-logs@3a523e4, on top ofc1fd3ee) has these pieces:<dataRoot>/logs/publish-timing.jsonl. QR handoff upload is logged too.Tests:
npm test169/169, typecheck clean,:protocol:testgreen, and the mainnet debug APK builds. Nothing is installed on a device yet, and no Dash was spent.Still open here:
The design for only-changed writes (#5) is in PR #10, as a doc-only change.
Timing MVP merged to main in PR #9 (merge
2b95a21; Auth 0.1.19 / versionCode 20, now installed on the tablet).Done:
Leaving this open for the remaining work:
Only-changed writes (#5) is the biggest win for write count and is in progress.