https://bugzilla.novell.com/show_bug.cgi?id=385711 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385711#c1 --- Comment #1 from Peter Poeml 2008-05-02 01:20:19 MST --- I'm almost certain that this won't speed anything up. It makes most sense (in terms of overhead and bandwidth usage) to keep a Keepalive HTTP connection saturated by requesting one file after the other. [This will give the fastest download possible, with the least overhead on client _and_ server. Keeping in mind that load caused on the server will (in the end) affect that same client also, is important.] Whether this is what libzypp is doing is unknown to me. I expect it isn't, because it after downloading one file it usually installs it first, before downloading the next, and Keepalive timeouts are commonly very short on busy servers (like 2-5 seconds). Yum does it that way (downloading all packages over a single connection and installing them after that all at once). I'm not counting methods to open several connections to the same server, which is what you suggest. You basically (could) suggest that the client opens 10 connections for the same 100MB file and requesting it in segments. That _can_ apparently speed up things for the client _if_ server-side bandwidth or server load is the bottleneck, and the client has bandwidth free. However, this goes on the cost of all other clients, and will eventually hurt the client itself. If everybody does it, everybody would have a disadvantage from it (much higher server load, much higher latencies). And we would need to install protection against it. What you _may_ consider is parallel downloads (in segments) from _different_ servers. Which leads to my proposal here http://en.opensuse.org/Libzypp/Failover It is okay (and can be useful) to retrieve several segments of the same big file from several servers. (This must be done in a way that the client bandwidth is not exceeded, because otherwise it would occupy slots on the server longer than necessary.) Metalinks (http://metalinker.org) support this transparently. You could talk to the zypp folks to integrate this in libzypp. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=385711 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385711#c3 --- Comment #3 from Peter Poeml 2008-05-02 02:43:58 MST --- I'll leave this for consideration by the yast/zypp team. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=385711 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385711#c4 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #4 from Michael Andres 2008-05-08 03:16:29 MST --- Also covered by FATE request #120340 - Run download and install in parallel. *** This bug has been marked as a duplicate of bug 370054 *** https://bugzilla.novell.com/show_bug.cgi?id=370054 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.