On Thu, 2006-09-07 at 18:08 +0100, Lance Davis wrote:
> CentOS 3 wont have the same issue because all updates are referenced via a
> round robin set of mirror.centos.org, which will always be seen as the
> same url by the proxy.
What's the problem with that scheme? It's hundreds of times faster
on my second and subsequent machines - and would be for anyone else
going through a proxy configured to cache large objects.
> >
> > Maybe those claimed 1.5 million users are really a few users or
> > locations
> > with a lot of machines... Letting proxies work as designed would
> > make sense to me.
>
> Well the issue is that you want a proxy to always hit the same mirror -
> (which you can configure) whereas we want to spread the load between the
> mirrors ...
What I want is for the default install to work using standard
cache techniques. The 'you can configure' concept only works if
you know everyone else sharing the same proxy and can pre-arrange
every file download with all of them which is pretty unlikely in
any organization large enough to even have a proxy. A scheme that
uses the same URL for the same file will always work automatically.
If you do this, spreading the load won't be an issue since there
will actually only be one download. If you can't use the same
set of mirrors as centos3, there has to be some way to make this
happen based on some computation that would be repeatable - perhaps
a server-side check that can see the requester's public source
address and give back the best mirror URL or a sorted list that
would always be the same for that source IP.
--
Les Mikesell
lesmikesell at gmail.com