Resilio Connect Agents transfer data directly between each other skipping any third party servers. The peer-to-peer nature of Resilio Connect implies that the data is split into pieces which are distributed across the decentralized network of the Agents. All the traffic between the Agents consists of two parts:
- payload (the user files);
- service traffic (files' metadata that the Agents exchange during synchronization, network protocols' headers, etc.).
The percentage of the service traffic in the overall traffic depends on the number of files, number of Agents, the network characteristics, and other environment parameters involved. Below is a cumulative table to illustrate the possible traffic overhead between two Windows Agents.
Return traffic is the traffic % sent from the destination back to the source Agent.
Protocol overhead includes protocol headers, handshakes, metainfo, merges, excluding retransmissions.
| Protocol | Number of files | Total size, MB | Transfer speed, Mbps | Return traffic | Protocols overhead, total |
|
LAN, 1 Gbps-limited |
|||||
|
utp3 |
1 |
5,120 5,120 |
728 671 |
0.03% 0.06% |
3.14% 0.28% |
| utp3 tcp |
100,000 100,000 |
977 977 |
75 82 |
2.44% 2.38% |
7.58% 5.82% |
| WAN, rtt 100ms, 1Gbps-limited, data loss is below 1% |
|||||
| utp3 tcp |
1 1 |
5,120 5,120 |
934 125 |
0.02% 0.03% |
3.27% 0.30% |
| utp3 tcp |
100,000 100,000 |
977 977 |
19 20 |
2.84% 3.61% |
4% |
| utp3 tcp |
500 500 |
5,000 5,000 |
699 147 |
0.02% 0.05% |
2.88% |