summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110112/002074.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/002074.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/002074.html')
-rw-r--r--zarb-ml/mageia-dev/20110112/002074.html149
1 files changed, 149 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110112/002074.html b/zarb-ml/mageia-dev/20110112/002074.html
new file mode 100644
index 000000000..178ab6889
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110112/002074.html
@@ -0,0 +1,149 @@
+<!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%20protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3C1294802984.32187.273.camel%40akroma.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002073.html">
+ <LINK REL="Next" HREF="002075.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%20protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3C1294802984.32187.273.camel%40akroma.ephaone.org%3E"
+ TITLE="[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download">misc at zarb.org
+ </A><BR>
+ <I>Wed Jan 12 04:29:43 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002073.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download
+</A></li>
+ <LI>Next message: <A HREF="002075.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#2074">[ date ]</a>
+ <a href="thread.html#2074">[ thread ]</a>
+ <a href="subject.html#2074">[ subject ]</a>
+ <a href="author.html#2074">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mardi 11 janvier 2011 &#224; 21:45 -0500, andre999 a &#233;crit :
+&gt;<i> Michael Scherer a &#233;crit :
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Le mardi 11 janvier 2011 &#224; 20:03 +0100, Marcello Anni a &#233;crit :
+</I>&gt;<i> &gt;&gt; hi all,
+</I>&gt;<i> &gt;&gt; i have one question (maybe it can be a proposal): is it possible to implement
+</I>&gt;<i> &gt;&gt; the torrent protocol to faster download the updates of the distro? it could be
+</I>&gt;<i> &gt;&gt; an interesting features for the coming Mageia releases
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; I think the issue of faster download could be simply taken care by
+</I>&gt;<i> &gt; having more mirror, or faster one.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; I had under the impression that some ISP throttle down bittorrent, and
+</I>&gt;<i> &gt; that it may not be very nat and firewall friendly..
+</I>&gt;<i>
+</I>&gt;<i> Some suggestions for faster downloads without bittorrent.
+</I>&gt;<i> 1) use aria2c (or a similar application), which uses multiple
+</I>&gt;<i> connections, defaulting to 5, and allows multiple mirrors.
+</I>&gt;<i> By default it starts by allocating space for the file to be downloaded,
+</I>&gt;<i> which allows non-sequential downloading of the file, facilitating faster
+</I>&gt;<i> downloading from multiple sites.
+</I>&gt;<i>
+</I>&gt;<i> 2) use mirrors which allow multiple connexions.
+</I>&gt;<i> (Of course, with download software that takes advantage of this.)
+</I>&gt;<i>
+</I>&gt;<i> 3) use multiple mirrors.
+</I>&gt;<i> (Again, according to download software.)
+</I>
+Theses 3 suggestions basically put X time the load of the mirror for
+each client. ( or on more mirror, for that matters ).
+
+And that's quite bad from the point of view of a mirror manager.
+
+For example, distrib-coffee could blacklist you if you do this, if you
+are not alone on your network connexion. And when we deployed this
+measure to protect the server, the limit was 2 connexion per address,
+since this was taking too much ressources on the old server ( each http
+request taking 1 process and so memory ). Hopefully, the hardware was
+upgraded but not everybody can afford 32g of ram and 8*2 ghz CPU.
+
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at distrib-coffee</A> ~]# grep -B 6 -A 3
+MaxConnPerIP /etc/httpd/conf.d/distrib-coffee.conf
+
+&lt;Directory /var/ftp/pub&gt;
+ order allow,deny
+ Allow from all
+ Options +Indexes +MultiViews +SymLinksIfOwnerMatch
+ &lt;IfModule mod_limitipconn.c&gt;
+ MaxConnPerIP 5
+ ErrorDocument 503 &quot;5 connections at the same time only allowed.&quot;
+ &lt;/IfModule&gt;
+&lt;/Directory&gt;
+
+So I think pissing off mirror maintainers is likely the wrong way of
+solving the problem ( who was not properly explained nor looked at
+besides &quot;it should be faster&quot; ).
+
+&gt;<i> 4) use ftp instead of http
+</I>
+Based on ?
+
+If this is based on using d-c, again, that's our custom QOS rules. If
+this is because of throttling on your provider, not everybody have the
+same provider, and so the same throttling.
+The only difference between http and ftp is that ftp server will likely
+scale better server side. But that should have no impact on file serving
+and download ( both nowadays use fast syscall, such as sendfile, etc ).
+
+&gt;<i> 5) use closer mirrors. (less delay in handshaking, etc.)
+</I>
+I think tcp handshake is not much a problem, given the fact it happen
+once per rpm, compared to the number of tcp packet for the rest of the
+download. Use wireshark to see.
+
+
+&gt;<i> In my case, using aria2c with 2 mirrors and the default 5 connexions is
+</I>&gt;<i> at least 3 times as fast as a single connexion (to my closest mirror).
+</I>&gt;<i> And a much greater improvement over other download options I've tried.
+</I>&gt;<i>
+</I>&gt;<i> I also have configured rpmdrake to use aria2c -- it seems to give me
+</I>&gt;<i> faster and more reliable updating, but I don't have any figures.
+</I>&gt;<i>
+</I>&gt;<i> aria2c is a console app, but it works well enough for me that I haven't
+</I>&gt;<i> (yet) bothered to install the available GUI frontend.
+</I>
+That's because it worked in your case that it would work for every
+possible case, especially without giving a proper analysis of the issue
+on your side.
+
+--
+Michael Scherer
+
+</PRE>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002073.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download
+</A></li>
+ <LI>Next message: <A HREF="002075.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#2074">[ date ]</a>
+ <a href="thread.html#2074">[ thread ]</a>
+ <a href="subject.html#2074">[ subject ]</a>
+ <a href="author.html#2074">[ 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>