On 15 May 2014 at 7:36, Daniel James wrote:
How hard is this page to generate? Is this something that can be generated "on the fly"? (instead of every day/hour/request/whatever)?
There's 123 repositories, so if 40 people hit the page within an hour, we're out of the limit. And I would guess if any link it posted to ML, the number of people who will click it will be higher than that.
A varnish reverse proxy would fix that in a cinch. Simply set a TTL of two minutes.
The response time for requests that aren't cached would be terrible, and it would be likely to fail whenever github is overwhelmed.
I'm not sure why you think that. https://ci.nedprod.com/ comes out of a varnish cache with the actual server sitting behind an OpenVPN in a home residential connection. Ping times are far more awful than they would be with a github API wrap, yet the CI website is perfectly okay to use. varnish knows how to serve stale content when the home DSL dies too. Rather more relevant to these discussions, a list of outstanding pull requests need - with minimal work - not exceed github limits. You can fire and forget. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/