1 |
It sounds interesting Ricardo. May I suggest that if you have the |
2 |
resources you set it up on your own LAN or something, then compare the |
3 |
results with rsync. |
4 |
|
5 |
You may need to get a few friends to do it over the net too, in order to try it on something less traffic friendly than your LAN. |
6 |
|
7 |
|
8 |
On Tue, 22 Mar 2005 23:58:19 +0000 |
9 |
Ricardo Correia wrote: |
10 |
|
11 |
> On Tuesday 22 March 2005 13:55, Patrick Lauer wrote: |
12 |
> > |
13 |
> > A few problems: |
14 |
> > - that .iso and the .zsync metadata need to be generated. More load on |
15 |
> > master server |
16 |
> > - isos don't allow easy access, e.g. writing a few bytes for a tricial |
17 |
> > bugfix |
18 |
> > - mkisofs might shuffle the data so that transferring one large file |
19 |
> > might cause more traffic than rsync does now |
20 |
> > |
21 |
> > I don't see the advantages over tar + binary diffs. |
22 |
> > |
23 |
> |
24 |
> You make valid points, but notice: |
25 |
> - The .zsync metadata doesn't have to be generated on the master server. |
26 |
> Anyone can do it right now. |
27 |
> - ISO's would have to be regenerated periodically. This could vary from every |
28 |
> 30 minutes to only once per day, we'd have to see how it works. |
29 |
> Personally I think every 30 minutes would be viable, but it's not really |
30 |
> necessary. Once per day would be enough and better than emerge-webrsync.. |
31 |
> |
32 |
> The advantage over tar + binary diffs: |
33 |
> - Client doesn't have to remove entire portage tree and extract the tar file |
34 |
> every sync. |
35 |
> - I think xdelta might be possible, but bsdiff would be impossible due to the |
36 |
> memory requirements for a tar this large. I don't really know how xdelta |
37 |
> performs CPU-wise and memory-wise.. |
38 |
> - It's simpler (only 2 files on the server and very few commands |
39 |
> necessary) :-) |
40 |
> -- |
41 |
> gentoo-dev@g.o mailing list |
42 |
|
43 |
-- |
44 |
Nick Rout |
45 |
Barrister & Solicitor |
46 |
Christchurch |
47 |
<http://www.rout.co.nz> |
48 |
<nick@×××××××.nz> |
49 |
|
50 |
-- |
51 |
gentoo-dev@g.o mailing list |