Repository navigation
Conversation
State the benchmark numbers once, reach Quick start sooner, and add a clone example. Keep a short comparison table and security summary in the README; the full comparison with footnotes and the full security model move to docs/comparison.md and docs/security-model.md.
The fast/safe/no-master-key claims now sit next to their evidence in a single SVG. The standalone Performance table is dropped from the README; docs/benchmarks.md already holds the full results and the reproduce script.
The 5,272 MiB figure came from a benchmark receiver with receive.unpackLimit=0. With default settings a small gcrypt push is unpacked and deduplicated on the host, so storage need not grow, even though the whole history is still transferred. Show fetch time instead, and say why gcrypt re-uploads: each state is a new parentless commit.
Fast now shows data sent, small-change and whole-history times, and peak memory as bar charts, including where git-remote-e2ee is slower or uses more memory. Safe and No master key sit below it.
It measured a receiver configured with receive.unpackLimit=0, which keeps every received pack. With Git's defaults a host can discard duplicate objects, so the row overstated gcrypt's lasting storage cost. The upload size row still shows what each push transfers.
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
1 participant
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.
README goes from 392 to 235 lines without dropping any claim.
docs/art/pillars.svg: Fast (data sent per one-line push, log scale), Safe (compare-and-swap rejects the losing push), No master key (fresh key per push and device; a revoked device gets none afterwards). Each pillar now sits next to its evidence.docs/benchmarks.mdalready holds the full table and the reproduce script. The "At a glance" table is gone too.cloneexample.docs/comparison.md.docs/security-model.md;SECURITY.mdlinks there.Docs-only change; relative links and anchors checked with a script.