Date: Wed, 2 Sep 2009 12:52:28 -0400 From: Wesley Shields <wxs@FreeBSD.org> To: Dmitry Marakasov <amdmi3@amdmi3.ru> Cc: Paul Schmehl <pschmehl_lists@tx.rr.com>, freebsd-ports@FreeBSD.org Subject: Re: Migration to new SourceForge URL scheme part 2, SFE and some statistics Message-ID: <20090902165228.GB20719@atarininja.org> In-Reply-To: <20090902162633.GB94573@hades.panopticon> References: <6B974976DD234EF08949F6A8@utd65257.utdallas.edu> <20090820164036.GA12998@hades.panopticon> <1250790054.45433.0.camel@hood.oook.cz> <20090821181232.GB59823@hades.panopticon> <1250882387.50625.0.camel@hood.oook.cz> <20090902031433.GA1304@hades.panopticon> <4A9E2505.1070306@FreeBSD.org> <20090902120508.2558236d@it.buh.tecnik93.com> <0B6596C6C29340D738A8A729@utd65257.utdallas.edu> <20090902162633.GB94573@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
(Trimming CC line...) On Wed, Sep 02, 2009 at 08:26:33PM +0400, Dmitry Marakasov wrote: > * Paul Schmehl (pschmehl_lists@tx.rr.com) wrote: > > > > In my case, over a few retries, switch is the fastest, followed by > > > surfnet. heatnet is only somewhere between 500-700K. > > > dfn, garr: and ovh fail. > > > > It might be way too much work for very little benefit, but network latencies > > being what they are, perhaps there should be a routine that runs periodically > > and adjusts the list according to some connectivity parameters? (Yeah, I know, > > easy for me to say. I don't have to write the code.) > > That's really too much work for a little benefit. The only thing > we really want from mirrors is fetchability, and as soon as we have > multiple mirrors that's achieved. Speed is a different issue and, > as my survey shows, mirrors can't be sorted once and forever to > satisfy the whole world, so if you feel like downloads are slow, > just add your favorte mirror into make.conf, like I did a long time > ago. The utility to do it automatically would be useful though, and > actually you can write one. Actually, something even more clever > could be written, similar to RANDOMIZE_MASTER_SITES, but based on > fetch speed feedback, but that'd be an overcomplication if you ask me. There is ports-mgmt/fastest_sites which sorts based upon round-trip time for the TCP handshake to complete. It's not accurate for download speeds but it provides a rough approximation for minimal effort. -- WXS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090902165228.GB20719>