aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* log why a deltatv5 days1-0/+6
|
* offered deltas lapsetv5 days2-7/+52
|
* fix: level means the peer has our headstv5 days1-6/+13
|
* fix: test links fail over cuts by nametv5 days1-5/+6
|
* dashboard: hop delaystv5 days2-3/+36
|
* throughput from delivered messagetv5 days3-3/+60
|
* hop delaystv5 days10-3/+211
|
* test links fail overtv5 days1-0/+105
|
* benchmark members joiningtv5 days2-8/+51
|
* benchmark delays by pathtv5 days3-0/+28
|
* tests count the changes senttv5 days1-5/+7
|
* document messages that overtaketv5 days1-4/+20
|
* fix: change publisher stops with the runtimetv5 days1-3/+8
|
* no reset for heads still on their waytv5 days1-1/+44
|
* benchmark what sync bytes aretv5 days4-3/+74
|
* changes from a peer never go backtv5 days2-0/+52
|
* older delivered messages leave us leveltv5 days2-36/+76
|
* benchmark where twice comes fromtv5 days3-6/+20
|
* resend only what is neededtv5 days2-27/+62
|
* benchmark delivered and twicetv5 days3-0/+58
|
* delivered means has all up to our headstv5 days1-13/+59
|
* any message taken as deliveredtv5 days6-47/+121
|
* slow round back offtv5 days7-10/+102
|
* tree messages need no answertv5 days6-10/+245
|
* hello again when heard fromtv5 days4-3/+75
| | | | | | 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_treestv6 days1-0/+3
|
* unanswered pull frees the slottv6 days3-4/+27
| | | | | | 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 ontv6 days3-5/+51
| | | | | | | 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_treestv6 days1-2/+52
|
* overdue sync asked after from thentv6 days3-49/+92
|
* pull after gracetv6 days3-5/+36
| | | | | | | | 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 lackingtv6 days7-15/+40
| | | | | | | 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 aftertv6 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 incidentstv6 days1-6/+21
|
* unanswered members not reachedtv7 days7-24/+143
|
* add member away benchmarktv7 days2-1/+36
|
* dashboard: show reach settv7 days2-2/+24
|
* links: only news pass ontv7 days1-6/+12
|
* dashboard: show writer treestv7 days5-26/+233
|
* add tree teststv7 days2-2/+144
|
* update architecture doctv7 days1-4/+7
|
* fixup 700, 701, 702tv7 days4-42/+43
|
* writers from authorstv7 days5-32/+75
|
* reach set for the sessiontv7 days6-22/+18
|
* add late arrivals benchmarktv7 days1-3/+49
|
* tree changes had alreadytv7 days3-5/+24
|
* announcement round counterstv7 days7-10/+53
|
* docs after treestv7 days3-10/+12
|
* announce what trees misstv7 days5-36/+125
|
* parallel propagation benchmarktv7 days2-15/+57
|