| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | benchmark where twice comes from | tv | 3 days | 2 | -4/+11 |
| | | |||||
| * | resend only what is needed | tv | 3 days | 1 | -1/+1 |
| | | |||||
| * | benchmark delivered and twice | tv | 3 days | 2 | -0/+30 |
| | | |||||
| * | any message taken as delivered | tv | 3 days | 2 | -13/+23 |
| | | |||||
| * | slow round back off | tv | 3 days | 2 | -5/+86 |
| | | |||||
| * | tree messages need no answer | tv | 3 days | 3 | -6/+40 |
| | | |||||
| * | hello again when heard from | tv | 3 days | 2 | -2/+19 |
| | | | | | | | 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 slot | tv | 4 days | 2 | -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. | ||||
| * | overdue sync asked after from then | tv | 4 days | 2 | -4/+4 |
| | | |||||
| * | pull after grace | tv | 4 days | 2 | -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 lacking | tv | 4 days | 4 | -10/+34 |
| | | | | | | | | 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 reached | tv | 5 days | 2 | -14/+43 |
| | | |||||
| * | links: only news pass on | tv | 5 days | 1 | -6/+12 |
| | | |||||
| * | dashboard: show writer trees | tv | 5 days | 1 | -26/+70 |
| | | |||||
| * | writers from authors | tv | 5 days | 3 | -27/+46 |
| | | |||||
| * | reach set for the session | tv | 5 days | 2 | -16/+10 |
| | | |||||
| * | tree changes had already | tv | 5 days | 1 | -4/+14 |
| | | |||||
| * | announcement round counters | tv | 5 days | 2 | -8/+23 |
| | | |||||
| * | docs after trees | tv | 5 days | 1 | -5/+6 |
| | | |||||
| * | announce what trees miss | tv | 5 days | 2 | -35/+115 |
| | | |||||
| * | order members by distance | tv | 5 days | 2 | -26/+59 |
| | | |||||
| * | replace eager links by trees | tv | 5 days | 6 | -137/+35 |
| | | |||||
| * | add writer trees | tv | 5 days | 5 | -27/+266 |
| | | |||||
| * | add writer tree benchmark | tv | 5 days | 1 | -0/+148 |
| | | |||||
| * | measure 2-hop neighbourhood | tv | 5 days | 7 | -8/+136 |
| | | |||||
| * | dashboard: show eager links on the map | tv | 5 days | 1 | -5/+19 |
| | | |||||
| * | add eager link counters | tv | 5 days | 2 | -0/+21 |
| | | |||||
| * | introduce eager links | tv | 5 days | 3 | -21/+100 |
| | | |||||
| * | skip neighbours with our heads | tv | 5 days | 2 | -15/+37 |
| | | |||||
| * | announcements answered only if heads differ | tv | 5 days | 4 | -7/+30 |
| | | |||||
| * | retry new peers before probing | tv | 5 days | 1 | -1/+1 |
| | | |||||
| * | probe list members | tv | 5 days | 3 | -6/+17 |
| | | |||||
| * | links: add failover | tv | 5 days | 1 | -14/+129 |
| | | |||||
| * | swarm: links by whom we reach | tv | 5 days | 2 | -12/+25 |
| | | |||||
| * | always announce new heads | tv | 5 days | 2 | -45/+9 |
| | | |||||
| * | links: when asking for a lot relays, do chunk | tv | 5 days | 1 | -17/+72 |
| | | |||||
| * | add budget for relayed LINKS | tv | 5 days | 1 | -1/+29 |
| | | |||||
| * | add links relay test | tv | 5 days | 1 | -0/+33 |
| | | |||||
| * | swarm: relay links messages | tv | 5 days | 2 | -24/+434 |
| | | |||||
| * | swarm: announce to whom writers can't reach | tv | 5 days | 2 | -28/+75 |
| | | |||||
| * | dashboard: double-click opens peer dashboard | tv | 5 days | 1 | -4/+61 |
| | | |||||
| * | add per-node traffic counts | tv | 5 days | 1 | -1/+9 |
| | | |||||
| * | probe when reachable | tv | 6 days | 2 | -1/+26 |
| | | |||||
| * | probe wakes peer worker | tv | 6 days | 1 | -2/+3 |
| | | |||||
| * | document: introduce patch log | tv | 6 days | 2 | -5/+5 |
| | | |||||
| * | large messages over slow links are deltas | tv | 6 days | 2 | -7/+40 |
| | | |||||
| * | links: wait for subscriber instead of ticker | tv | 6 days | 1 | -6/+16 |
| | | |||||
| * | peer worker forget records on change | tv | 6 days | 4 | -4/+28 |
| | | |||||
| * | peer worker sleeps until deadline, not fixed time | tv | 6 days | 7 | -14/+109 |
| | | |||||
| * | bootstrap: replace pull by progress notify | tv | 6 days | 2 | -2/+15 |
| | | |||||
