aboutsummaryrefslogtreecommitdiffstats
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
...
* document messages that overtaketv8 days1-4/+20
|
* any message taken as deliveredtv8 days1-7/+9
|
* slow round back offtv8 days2-5/+10
|
* tree messages need no answertv8 days1-3/+10
|
* hello again when heard fromtv8 days1-1/+4
| | | | | | While we wait for a peer's HELLO_REPLY, anything else that comes from it makes our HELLO go again at once, at most once a second, instead of when the backoff says.
* unanswered pull frees the slottv8 days1-3/+4
| | | | | | When the answer to a pull is overdue (the sync reply timeout: 1 s in the simtests, 10 s in production), the pull gives up the slot, and the next waiting neighbour is pulled at once.
* no heal while both move ontv8 days2-2/+2
| | | | | | | The heal clock now also restarts when our heads and the peer's have both changed since the last STATUS that showed them differing. While writes go on, two neighbours's heads differ because of changes still on their way, and that alone no longer leads to a heal.
* pull after gracetv8 days1-1/+3
| | | | | | | | Before pulling, a node waits one measured round trip to the announcer (1 s at most) and pulls only what is still missing. If the round trip isn't known yet, it pulls at once, as now. On the clean benchmark links the round trip is a few milliseconds, so those scenarios shouldn't change.
* announcements answered when lackingtv8 days2-3/+4
| | | | | | | A neighbour now answers an announcement only if it lacks some of the announced heads. Heads that merely differ are no longer enough, since they do while writes go on. The check reads the document, so it runs off the message consumer, as the pull check already does.
* unanswered members not reachedtv9 days2-6/+11
|
* add member away benchmarktv9 days1-1/+2
|
* dashboard: show reach settv9 days1-0/+1
|
* dashboard: show writer treestv9 days2-0/+44
|
* update architecture doctv9 days1-4/+7
|
* writers from authorstv9 days1-5/+7
|
* reach set for the sessiontv9 days2-3/+5
|
* tree changes had alreadytv9 days1-1/+3
|
* announcement round counterstv9 days2-1/+7
|
* docs after treestv9 days1-1/+1
|
* announce what trees misstv9 days1-1/+6
|
* parallel propagation benchmarktv9 days1-1/+3
|
* quicker propagation benchmarktv9 days1-1/+2
|
* order members by distancetv9 days1-4/+6
|
* replace eager links by treestv9 days5-32/+13
|
* add writer treestv9 days1-0/+16
|
* add writer tree benchmarktv9 days1-1/+4
|
* measure 2-hop neighbourhoodtv9 days2-1/+20
|
* add propagation benchmarktv9 days1-0/+8
|
* dashboard: show eager links on the maptv9 days2-4/+9
|
* add eager link counterstv9 days2-1/+10
|
* introduce eager linkstv9 days2-1/+15
|
* skip neighbours with our headstv10 days2-2/+5
|
* announcements answered only if heads differtv10 days2-3/+4
|
* retry new peers before probingtv10 days1-1/+3
|
* probe list memberstv10 days1-1/+3
|
* links: add failovertv10 days1-0/+6
|
* swarm: links by whom we reachtv10 days1-1/+2
|
* always announce new headstv10 days2-7/+6
|
* dashboard: neater graph title & legendtv10 days1-8/+9
|
* dashboard: legend doesn't interfere with graphtv10 days1-2/+4
|
* links: when asking for a lot relays, do chunktv10 days1-2/+3
|
* add budget for relayed LINKStv10 days1-3/+4
|
* add stream heartbeattv10 days4-4/+14
|
* dashboard: add console clear buttontv10 days1-1/+1
|
* dashboard: indicate console followingtv10 days1-1/+2
|
* config: dashboard-url requires dashboard featuretv10 days1-1/+2
|
* dashboard: pass state to next dashboardtv10 days1-2/+10
|
* add links relay testtv10 days1-0/+5
|
* swarm: relay links messagestv10 days2-3/+22
|
* swarm: announce to whom writers can't reachtv10 days2-2/+6
|