On Tue, Jun 5, 2012 at 8:28 AM, Mark Phippard <markp...@gmail.com> wrote: > Keep in mind that this is not about server load, they are looking at > this from bandwidth. So a cache in front of the server would not help > them at all. Eclipse.org has a 10MB Internet link that is almost > always saturated. > > Also, if it was not clear, Subversion is not involved here. This is a > plain Apache server.
IMO, having a 10Mbps link (if that is indeed the case) is probably the root of the problem...that's ridiculously underprovisioned for a public site. Any type of update checks for a heavily used product no matter what the underlying protocol is would saturate that once they get enough users. An easy thing for them to have done (for example) is to shove the check on their mirrors or a CDN (hi Fastly!) or something similar. This goes back to having a simple protocol which is the antithesis of the REPORT call in ra_neon. Having a simple straightforward protocol allows you to easily drop in caches - REPORT won't let you do that as the responses are too specific to the user to permit any type of caching which will limit your options when you do hit load. -- justin
