diff options
| author | tv <tv@krebsco.de> | 2026-11-05 04:36:58 +0100 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-05 04:36:58 +0100 |
| commit | c7226385f3765b2a72b7b4d95129fb20fec58d5c (patch) | |
| tree | 6d6f6e1b6c58c16789551068f2daa8e19524abe2 /docs/development.md | |
| parent | 39980623f81e9e75f142f55a35794bf7a53aa38b (diff) | |
push changes experiment
Diffstat (limited to 'docs/development.md')
| -rw-r--r-- | docs/development.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/development.md b/docs/development.md index 519d64c..e09abbc 100644 --- a/docs/development.md +++ b/docs/development.md @@ -26,7 +26,8 @@ and with Mycelium's round trips, each link its own; and Tor's, with some slow ci members joining during the writes; several minutes, or one scenario alone with `BENCH_SCENARIO`, part of its name: `BENCH_SCENARIO=NAT`; all at once with `BENCH_PARALLEL=1`, faster on many cores, though sharing them makes delays come out -somewhat higher; and in `bench_bridge`, large values from a writer on a fast transport +somewhat higher; with `BENCH_PUSH=1`, changes along writers' trees go as they are +rather than in Automerge sync messages, an experiment to measure against; and in `bench_bridge`, large values from a writer on a fast transport through a bridge to a node on a slow one: what that node gets as sync messages and as blobs against what was written, 200 values unless `BENCH_BRIDGE_WRITES` says otherwise, over a fast link of 1 GiB/s and 5 ms round trips and a slow one of 50 |
