OXYGENHUB

Commit: no second snapshot after a commit that took everything issue #93 closed: completed andymccall opened this · 1 comment

andymccall

Profiled on VS Code at 19,978 commits (oxy commit -m M README.md, one edited file): 482 ms against Git's 27 ms.

  • snapshot before the commit: 112 ms (82 ms loading the base's history: the state index 41 ms, validate 8 ms)
  • extend the state: 33 ms
  • record: 132 ms, of which the store's fsync 100 ms (kept: durability, spec §13.6)
  • a second snapshot after the commit: 137 ms

The second snapshot is the CLI counting paths left uncommitted after a commit with paths. When the selection took every operation of the working copy (not partial), nothing is left, so the count is known without a snapshot.

Then look at the base load: 82 ms to load a state the state index holds.

refs issue #81

andymccall referenced by change 7505194116e7 on main ·

andymccall referenced by change ac03130a2b95 on main ·

andymccall

The second snapshot is gone: oxy commit counts what is left only when the selection took part of the working copy (commit_selection_partial), so a commit that took everything snapshots once. What remains here, the 82 ms base load, is issue #94's work (read the state index lazily); closing this in favour of it.

andymccall closed ·