| 1 |
Hi, |
| 2 |
|
| 3 |
I am currently embarking on a plan to redo our existing rsync[0] mirror |
| 4 |
network. The current network has aged a bit. Its likely too large and is |
| 5 |
under-maintained. I think in the ideal case we would instead pivot this |
| 6 |
project to scaling out our git mirror capabilities and slowly migrate all |
| 7 |
consumers to pulling the git tree directly. To that end, I'm looking for |
| 8 |
blockers as to why various customers cannot switch to pulling the gentoo |
| 9 |
ebuild repository from git[1] instead of rsync. |
| 10 |
|
| 11 |
So for example: |
| 12 |
|
| 13 |
- bandwidth concerns (preferably with documentation / data.) |
| 14 |
- Firewall concerns |
| 15 |
- CPU concerns (e.g. rsync is great for tiny systems?) |
| 16 |
- Disk usage for git vs rsync |
| 17 |
- Other things i have not thought of. |
| 18 |
|
| 19 |
-A |
| 20 |
|
| 21 |
[0] This excludes emerge-webrsync; which I don't plan on touching. |
| 22 |
[1] Rich talked about some downsides earlier at |
| 23 |
https://lwn.net/Articles/759539/; but while these are challenges (some |
| 24 |
fixable) they are not necessarily blockers. |
Archives