summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110112/002085.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20110112/002085.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/20110112/002085.html')
-rw-r--r--zarb-ml/mageia-dev/20110112/002085.html142
1 files changed, 142 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110112/002085.html b/zarb-ml/mageia-dev/20110112/002085.html
new file mode 100644
index 000000000..0fe9711cd
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110112/002085.html
@@ -0,0 +1,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>