diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110118/002216.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110118/002216.html | 122 |
1 files changed, 122 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110118/002216.html b/zarb-ml/mageia-dev/20110118/002216.html new file mode 100644 index 000000000..5ea3b1a6b --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002216.html @@ -0,0 +1,122 @@ +<!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=%3C4D354094.6070407%40animeneko.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002215.html"> + <LINK REL="Next" HREF="002219.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download</H1> + <B>Motoko-chan</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=%3C4D354094.6070407%40animeneko.net%3E" + TITLE="[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download">motokochan at animeneko.net + </A><BR> + <I>Tue Jan 18 08:26:12 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI>Next message: <A HREF="002219.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#2216">[ date ]</a> + <a href="thread.html#2216">[ thread ]</a> + <a href="subject.html#2216">[ subject ]</a> + <a href="author.html#2216">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +><i> However I feel that +</I>><i> 4) It is reasonable for downloaders to use multiple connexions per +</I>><i> mirror, as long as they don't bypass the controls put in place by the +</I>><i> mirror. Not only reasonable, but actually desirable in terms of using +</I>><i> otherwise unused download capacity that occurs from time to time, and +</I>><i> thus enhancing general download access. +</I> +This method only works in the following situations: + +- The mirror limits the speed of each individual connection +- You use multiple mirrors to download +- If applying to a single file across multiple mirrors, the mirrors +support transfer of selective portions of the requested file + +In the first situation, the mirror maintainer usually has a good reason +for limiting connection speed. If their limit is very low, you should +contact the project they are mirroring and suggest they be dropped as an +official mirror. Going around admin-imposed limitations is bad manners +at the very least and will either get you banned or cause further +restrictions that will harm everyone. + +In the second situation, you are now taking the bandwidth of multiple +mirrors, increasing the overall load on the mirror network. Use of four +mirrors means you just took up resources that three other people could +have been using. Effectively, you're being greedy to the detriment of +the community. + +The third situation presumes a certain configuration that isn't +necessarily true. It also has the same problems as the second situation. + +><i> +</I>><i> There is another factor that may not have been considered. Many +</I>><i> downloaders will be slowed by their internet access or other +</I>><i> non-mirror factors, which will very much increase the likelihood that +</I>><i> mirrors have unused bandwidth at various times. Increasing the +</I>><i> utility -- from both sides -- of multiple connexions. +</I> +That is an argument against multi-mirror downloads. Most mirror servers +will have good bandwidth for their region. In general, the user's +connection will be a bottleneck. The overhead of maintaining multiple +connections can actually _slow down_ the downloads. + +As for torrents, there exists a large problem in that there are several +ways to handle such things (torrent per file, torrent per directory, +etc) and on every change you would need the torrent to be regenerated +and seeds to be established. If you are doing this on something with a +lot of file churn such as a development trunk, you run into a ton of +management overhead for handling the torrents. Even if you start with +web seeds, you now strain your mirrors by requesting that they be active +in seeding a bunch of torrents. + +Bittorrent makes good sense in one big situation: you have a single +large or multiple files that will be widely downloaded and distributed, +and the downloaders are likely to leave their download tool (torrent +application) running after download. This is especially useful when it's +going to be a large, but temporary, demand such as ISO files at release +time. While some mirrors might be able to handle a 200-300% increase in +traffic, others may not. It's expensive to provision at that capacity +when such a thing only happens twice a year for a week or maybe two. In +such cases, torrents make very good sense as they help reduce the peak +demand on your mirrors. + + - Michael +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI>Next message: <A HREF="002219.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#2216">[ date ]</a> + <a href="thread.html#2216">[ thread ]</a> + <a href="subject.html#2216">[ subject ]</a> + <a href="author.html#2216">[ 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> |