On Mon, 19 Dec 2011 13:51:02 +0100 Zdeněk Pavlas <[email protected]> wrote:
> The fastestmirror plugin tries to find the fastest mirror > by timing a null TCP connect(), so usually 2x RTT. > > However, the value measured includes host DNS lookup overhead, > which is completely unrelated. So, perform it outside > the connect() statement. Applying minor patches to fastestmirror doesn't fix the underlying problem that fastestmirror doesn't measure what you actually care about - transfer of files - not connect() time. A plan in the past you may want to pursue is this: 1. have urlgrabber write out performance info for each mirror per-repo. 2. Use that info to determine which mirror is fastest - and in general for sorting the mirror list. -sv _______________________________________________ Yum-devel mailing list [email protected] http://lists.baseurl.org/mailman/listinfo/yum-devel
