aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* drop full mesh stattv3 days5-15/+8
|
* bench mycelium round tripstv3 days2-2/+35
|
* delta from held headstv3 days5-30/+88
|
* offer again ungeneratedtv3 days3-33/+141
|
* stale delta offerstv3 days3-0/+82
|
* blob window growstv3 days1-5/+10
|
* delta known to sendertv3 days3-7/+16
|
* delta propagationtv3 days3-3/+20
|
* benchmark bridge fast linktv3 days2-19/+25
|
* sim links push backtv3 days1-18/+33
|
* benchmark bridge slow linktv3 days2-9/+21
|
* benchmark bridgetv3 days2-1/+124
|
* sim link ratestv3 days1-1/+49
|
* one delta at a timetv3 days3-10/+58
|
* time blob messagestv3 days11-10/+59
|
* log why a deltatv3 days1-0/+6
|
* offered deltas lapsetv3 days2-7/+52
|
* fix: level means the peer has our headstv3 days1-6/+13
|
* fix: test links fail over cuts by nametv4 days1-5/+6
|
* dashboard: hop delaystv4 days2-3/+36
|
* throughput from delivered messagetv4 days3-3/+60
|
* hop delaystv4 days10-3/+211
|
* test links fail overtv4 days1-0/+105
|
* benchmark members joiningtv4 days2-8/+51
|
* benchmark delays by pathtv4 days3-0/+28
|
* tests count the changes senttv4 days1-5/+7
|
* document messages that overtaketv4 days1-4/+20
|
* fix: change publisher stops with the runtimetv4 days1-3/+8
|
* no reset for heads still on their waytv4 days1-1/+44
|
* benchmark what sync bytes aretv4 days4-3/+74
|
* changes from a peer never go backtv4 days2-0/+52
|
* older delivered messages leave us leveltv4 days2-36/+76
|
* benchmark where twice comes fromtv4 days3-6/+20
|
* resend only what is neededtv4 days2-27/+62
|
* benchmark delivered and twicetv4 days3-0/+58
|
* delivered means has all up to our headstv4 days1-13/+59
|
* any message taken as deliveredtv4 days6-47/+121
|
* slow round back offtv4 days7-10/+102
|
* tree messages need no answertv4 days6-10/+245
|
* hello again when heard fromtv4 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_treestv4 days1-0/+3
|
* unanswered pull frees the slottv4 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 ontv4 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_treestv4 days1-2/+52
|
* overdue sync asked after from thentv4 days3-49/+92
|
* pull after gracetv4 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 lackingtv4 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 aftertv4 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 incidentstv5 days1-6/+21
|
* unanswered members not reachedtv5 days7-24/+143
|