How to prevent fetching from macports mirrors
Rainer Müller
raimue at macports.org
Tue Mar 20 16:39:23 UTC 2018
On 2018-03-20 15:17, Mojca Miklavec wrote:
> On 20 March 2018 at 03:37, Ryan Schmidt wrote:
>> On Mar 19, 2018, at 11:31, Mojca Miklavec wrote:
>>
>>> MacPorts sometimes spends 30 seconds trying to fetch files from
>>> https://distfiles.macports.org or some other mirror server when I
>>> *know* the files are not there (when writing a new port or updating an
>>> existing one).
>>
>> It should take well under a second for it to respond with a 404. I don't know why it would take anywhere close to 30 seconds for that.
>
> I don't know that either. Server overload maybe? :)
> I'm not seeing that problem on other mirrors, but
> distfiles.macports.org is often slow to respond.
If MaxCDN does not have any cached state for the file, which obviously
will be the case for new versions, it will first have to check the
origin mirror. This might take a while, although I never encountered
such a long delay. It probably also depends from which "edge location"
the CDN serves you and their peering.
https://www.maxcdn.com/features/network/#full-pop-list
> The annoying thing is that 15 servers are tried before actually trying
> the one specified in master_sites.
>
> Btw, thanks a lot for the hint. The option is much easier to remember in 2.5 :)
The annoyance of unnecessarily hitting lots of mirrors is exactly what
made me add this flag. :-)
Rainer
More information about the macports-dev
mailing list