summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110112/002085.html
blob: 0fe9711cd4b7b98e42ce7aa635268cc8c16651e0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Proposal for Mageia: implement bitorrent	protocol to allow updates download
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%09protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3C4D2DB66C.2020801%40laposte.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="002082.html">
   <LINK REL="Next"  HREF="002087.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Proposal for Mageia: implement bitorrent	protocol to allow updates download</H1>
    <B>andre999</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%09protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3C4D2DB66C.2020801%40laposte.net%3E"
       TITLE="[Mageia-dev] Proposal for Mageia: implement bitorrent	protocol to allow updates download">andr55 at laposte.net
       </A><BR>
    <I>Wed Jan 12 15:10:52 CET 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="002082.html">[Mageia-dev] Proposal for Mageia: implement bitorrent	protocol	to allow updates download
</A></li>
        <LI>Next message: <A HREF="002087.html">[Mageia-dev] Proposal for Mageia: implement bitorrent	protocol	to allow updates download
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#2085">[ date ]</a>
              <a href="thread.html#2085">[ thread ]</a>
              <a href="subject.html#2085">[ subject ]</a>
              <a href="author.html#2085">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Olivier Thauvin a &#233;crit :
&gt;<i> * andre999 (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>) wrote:
</I>&gt;&gt;<i> Michael Scherer a &#233;crit :
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> Le mardi 11 janvier 2011 &#224; 20:03 +0100, Marcello Anni a &#233;crit :
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> In my case, using aria2c with 2 mirrors and the default 5 connexions is
</I>&gt;&gt;<i> at least 3 times as fast as a single connexion (to my closest mirror).
</I>&gt;&gt;<i> And a much greater improvement over other download options I've tried.
</I>&gt;<i>
</I>&gt;<i> This is a selfish point of view, nothing is important except the result
</I>&gt;<i> on your side.
</I>
Sorry, but this can't be serious.
If a user is to download say a 4,7G DVD iso, it is 4,7G if the user uses 
one or 5 connexions, from one or 5 mirrors.
And if the 5 connexions go to 5 different mirrors, that is only 20% per 
mirror.
Globally, if the same files are downloaded, the same amount of data is 
downloaded.
What we are talking about here, from the user side, is downloading 
faster, if the capacity is _available_ on the network of mirrors.
Nothing more, nothing less.

There are many mirrors which provide multiple connexions, with a very 
large bandwidth.  If users don't use the available connexions on these 
servers, other mirrors will be more heavily impacted.
So, as I said in another post on this thread, it is win-win for both 
users and mirrors.

&gt;<i> But as I can see the results of such thing on distrib-coffee I can tell:
</I>&gt;<i> - often the bandwidth limititation is client side (eg you, with your DSL
</I>&gt;<i>    connection, and not the mirror, with 100mbits/s or more)
</I>&gt;<i> - all mirrors have limit, and when the max connection will be reached
</I>&gt;<i>    the mirror will stop serving you (download will be very faster !)
</I>
That is the advantage of applications like aria2c.  They search 
available connexions from the urls (mirrors) given, and choose which 
give the fastest downloads.  The number of connexions vary according to 
the conditions.  With the default of 5 connexions, aria2c tries to 
maintain 5 connexions, but in practice fluctuates (dynamically) between 
3 and 5, according to conditions.  (From my experience.)

Think of it another way.
Scenerio 1)  Suppose at this moment the mirror network has 20% free 
capacity.  We download without multiple connections or multiple mirrors, 
without using this excess capacity.  In one hour we are still 
downloading, at a time when there is no free capacity.

Scenerio 2) We download using multiple connexions and multiple mirrors, 
accelerating the downloads with the otherwise unused 20% free capacity. 
  In one hour, most of our downloads are finished, thus leaving free 
capacity.

Just who is served by scenerio 1 ?
The users that don't have access, or the mirrors that are overloaded ?

&gt;<i> Of course, if in the case I don't blacklist mageia and deny download via
</I>&gt;<i> http/ftp to save my mirror (d-c is already under heavy load).
</I>&gt;<i>
</I>&gt;<i> So, no, don't donwload several times from a mirror.
</I>
The solution ?  If a mirror can't handle multiple connexions, restrict 
it in some way.  Many mirrors do.  Either all the time, or from time to 
time.  Or throttle the transfer speed.
Just do whatever works best for the mirror in question.
However let users use the capacity available.  Because it may not be 
available in one hour, or even 5 minutes.

&gt;<i> BTW: on distrib-coffee bandwidth is regulated by IP, not connection,
</I>&gt;<i> downloading 5 times will not be faster than 1.
</I>
Essentially the same thing.  Great, if it works for the mirror.

aria2c senses the the bandwidth dynamically, and reacts accordingly. 
I'm sure that many other applications do the same thing.
Don't forget that much of the increase in download speed comes from 
using multiple mirrors. (Clearly indicated in the aria2c documentation, 
and verified in my usage.)

Why not think globally ?

another 2 cents :)

-- 
Andr&#233;
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="002082.html">[Mageia-dev] Proposal for Mageia: implement bitorrent	protocol	to allow updates download
</A></li>
	<LI>Next message: <A HREF="002087.html">[Mageia-dev] Proposal for Mageia: implement bitorrent	protocol	to allow updates download
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#2085">[ date ]</a>
              <a href="thread.html#2085">[ thread ]</a>
              <a href="subject.html#2085">[ subject ]</a>
              <a href="author.html#2085">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>