aboutsummaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* delivered means has all up to our headstv7 days1-13/+59
|
* any message taken as deliveredtv7 days5-40/+112
|
* slow round back offtv7 days5-5/+92
|
* tree messages need no answertv7 days5-7/+235
|
* hello again when heard fromtv7 days3-2/+71
| | | | | | 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.
* bump pulled_changes_go_along_their_writers_treestv8 days1-0/+3
|
* unanswered pull frees the slottv8 days2-1/+23
| | | | | | 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 days1-3/+49
| | | | | | | 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.
* bump pulled_changes_go_along_their_writers_treestv8 days1-2/+52
|
* overdue sync asked after from thentv8 days3-49/+92
|
* pull after gracetv8 days2-4/+33
| | | | | | | | 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 days5-12/+36
| | | | | | | 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 sync asked aftertv8 days1-6/+28
| | | | | An overdue sync answer is now followed by a PING too, and the peer stays reached once it answers the PING.
* simtest: benchmark incidentstv8 days1-6/+21
|
* unanswered members not reachedtv9 days5-18/+132
|
* add member away benchmarktv9 days1-0/+34
|
* dashboard: show reach settv9 days1-2/+23
|
* links: only news pass ontv9 days1-6/+12
|
* dashboard: show writer treestv9 days3-26/+189
|
* add tree teststv9 days2-2/+144
|
* fixup 700, 701, 702tv9 days4-42/+43
|
* writers from authorstv9 days4-27/+68
|
* reach set for the sessiontv9 days4-19/+13
|
* add late arrivals benchmarktv9 days1-3/+49
|
* tree changes had alreadytv9 days2-4/+21
|
* announcement round counterstv9 days5-9/+46
|
* docs after treestv9 days2-9/+11
|
* announce what trees misstv9 days4-35/+119
|
* parallel propagation benchmarktv9 days1-14/+54
|
* quicker propagation benchmarktv9 days1-14/+21
|
* order members by distancetv9 days3-37/+63
|
* replace eager links by treestv9 days23-307/+48
|
* add writer treestv9 days11-33/+323
|
* add writer tree benchmarktv9 days1-0/+148
|
* measure 2-hop neighbourhoodtv9 days21-10/+230
|
* add propagation benchmarktv9 days3-1/+396
|
* dashboard: show eager links on the maptv9 days6-7/+65
|
* add eager link counterstv9 days4-0/+47
|
* introduce eager linkstv9 days14-24/+195
|
* skip neighbours with our headstv9 days3-15/+42
|
* announcements answered only if heads differtv9 days12-9/+46
|
* retry new peers before probingtv9 days2-6/+38
|
* probe list memberstv9 days4-9/+25
|
* links: add failovertv9 days1-14/+129
|
* swarm: links by whom we reachtv9 days3-12/+73
|
* always announce new headstv9 days3-45/+62
|
* dashboard: neater graph title & legendtv9 days1-17/+37
|
* dashboard: legend doesn't interfere with graphtv9 days1-3/+13
|
* links: when asking for a lot relays, do chunktv9 days1-17/+72
|
* add budget for relayed LINKStv9 days1-1/+29
|