Douglas Bell wrote:
Over the QA Hackathon, we added Fastly caching to the cpantesters. That error
appears when the cache can't access cpantesters itself to update its cache.
We're still trying to get everything figured out here.
Fastly does geocaching, so you get a local version faster. It caches for about
an hour, since that's approximately how often the static site gets updated
anyway. It doesn't seem to have a way to set how long it waits for a response
from cpantesters though. The cache not waiting long enough is my current theory
on why this problem is happening.
---
Could be, though *subjectively*, it seems to be taking alot longer
to get responses of any kind -- and then more often than not (>50%) of the
time it is a timeout error.
Maybe the varnish layer resulted in an overall slowdown due to machine
memory or CPU constraints?
We should've just gone with Memoize for back-end.... of course last
I looked at it, it didn't seem to have alot of control for how often
it's static version would get updated (i.e. -- like 'never': *oh well*)
seems like its often a matter of not enough cache or cash to throw at
solutions...
thanks for the update...
