colineonset

Public

Onset: version control where nobody waits and nothing gets lost. The on command, its core and onset-server.

CodeIssuesChange requestsActionsDiscussionsCommitsBranchesReleasesSearchContributorsCompare

Code Issues Change requests Actions Discussions Commits Branches Releases Search Contributors Compare

Upstream

Docs Pricing Support Changelog

coline/onset

colineonset

Public

Onset: version control where nobody waits and nothing gets lost. The on command, its core and onset-server.

CodeIssuesChange requestsActionsDiscussionsCommitsBranchesReleasesSearchContributorsCompare

Code Issues Change requests Actions Discussions Commits Branches Releases Search Contributors Compare

perf(vcs): landing 10x cheaper on the host; git view paced and switchable

Radin committed …

Author: Radin · radin@coline.appOct 28, 2026 at 01:14
Committer: Radin · radin@coline.appOct 28, 2026 at 01:14
Parents: 961b2e1507a6

perf(vcs): landing 10x cheaper on the host; git view paced and switchable

- Edits only read and rebuild the folders on their paths, not the whole
  tree (7.7 ms of CPU a landing to 0.7 ms, the same at 20,000 files).
- Secret patterns run only on lines holding their fixed text.
- Small-object bytes are counted, not summed on every landing; settings
  are read once.
- The git view pushes at most once a second, many versions a push, sends
  the core only the git IDs each version needs, and reuses one zlib stream.
- Objects a landing makes count against the core's cache cap (32 MiB), so
  a project landing for hours stays under the isolate's 128 MB.
- Token and repository lookups: one at a time per key, so a burst asks
  Upstream once.
- vcs settings git=off|on; the project view says how far the git view is
  behind.
- apps/vcs/bench/land.mjs runs the project object in Node to time and
  profile landing; tests/load.mjs loads a live host over HTTP.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

7 files changed+415−53

← Back to history