aboutsummaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* fix: test links fail over cuts by nametv7 days1-5/+6
|
* dashboard: hop delaystv7 days1-3/+35
|
* throughput from delivered messagetv7 days2-2/+59
|
* hop delaystv7 days8-3/+178
|
* test links fail overtv7 days1-0/+105
|
* benchmark members joiningtv7 days1-5/+48
|
* benchmark delays by pathtv7 days3-0/+28
|
* tests count the changes senttv7 days1-5/+7
|
* fix: change publisher stops with the runtimetv7 days1-3/+8
|
* no reset for heads still on their waytv7 days1-1/+44
|
* benchmark what sync bytes aretv7 days4-3/+74
|
* changes from a peer never go backtv7 days2-0/+52
|
* older delivered messages leave us leveltv7 days2-36/+76
|
* benchmark where twice comes fromtv7 days3-6/+20
|
* resend only what is neededtv7 days2-27/+62
|
* benchmark delivered and twicetv7 days3-0/+58
|
* 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_treestv7 days1-0/+3
|
* unanswered pull frees the slottv7 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 ontv7 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_treestv7 days1-2/+52
|
* overdue sync asked after from thentv7 days3-49/+92
|
* pull after gracetv7 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 lackingtv7 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 aftertv7 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 reachedtv8 days5-18/+132
|
* add member away benchmarktv8 days1-0/+34
|
* dashboard: show reach settv8 days1-2/+23
|
* links: only news pass ontv8 days1-6/+12
|
* dashboard: show writer treestv8 days3-26/+189
|
* add tree teststv8 days2-2/+144
|
* fixup 700, 701, 702tv8 days4-42/+43
|
* writers from authorstv8 days4-27/+68
|
* reach set for the sessiontv8 days4-19/+13
|
* add late arrivals benchmarktv8 days1-3/+49
|
* tree changes had alreadytv8 days2-4/+21
|
* announcement round counterstv8 days5-9/+46
|
* docs after treestv8 days2-9/+11
|
* announce what trees misstv8 days4-35/+119
|
* parallel propagation benchmarktv8 days1-14/+54
|
* quicker propagation benchmarktv8 days1-14/+21
|
* order members by distancetv8 days3-37/+63
|
* replace eager links by treestv8 days23-307/+48
|
* add writer treestv8 days11-33/+323
|
* add writer tree benchmarktv8 days1-0/+148
|