On Thu, Jun 2, 2011 at 12:24 AM, Chris Hanks
christopher.m.ha...@gmail.comwrote:
Huh. I remembered seeing somebody from Heroku say that they had their
Varnish servers set up in a hash ring, which I thought would mean this
kind of effect wouldn't happen, but I guess it does. It looks like
they
show my
app processing the request and subsequent requests for the same
resource continue to hit my app.
Any guidance on how to troubleshoot this further to figure out why
Varnish isn't caching?
Here are the response headers from Heroku:
HTTP/1.1 200 OK
Server: nginx/0.7.67
Date: Wed
to hit my app.
Any guidance on how to troubleshoot this further to figure out why
Varnish isn't caching?
What stack and how many dynos is this app running? On Bamboo the setup is
something like 1 varnish instance per dyno. If you have 5 dynos, it's going
to hit your app at most 5 times before it's
per
the Heroku docs but when I request the resource, Heroku logs show my
app processing the request and subsequent requests for the same
resource continue to hit my app.
Any guidance on how to troubleshoot this further to figure out why
Varnish isn't caching?
Here are the response headers from
the Heroku docs but when I request the resource, Heroku logs show my
app processing the request and subsequent requests for the same
resource continue to hit my app.
Any guidance on how to troubleshoot this further to figure out why
Varnish isn't caching?
Here are the response headers
So after hearing back from support it looks like Varnish is caching
just fine it's just that they have a bunch of Varnish servers and the
chances of you hitting the same one twice is pretty low. Try firing
off 10 simultaneous requests and you'll see some of them served from
Varnish cache. Nice
simultaneous requests it hits my Rails app 10
times before everything starts being served from Varnish.
Anyway, thanks for looking into it, Craayzie.
On Jun 1, 7:24 pm, craayzie flesh...@gmail.com wrote:
So after hearing back from support it looks like Varnish is caching
just fine it's just
out why
Varnish isn't caching?
Here are the response headers from Heroku:
HTTP/1.1 200 OK
Server: nginx/0.7.67
Date: Wed, 01 Jun 2011 00:24:28 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
ETag: 8b8a779a2522e7a42fc663b76a088763
X-UA-Compatible: IE=Edge,chrome=1
X-Runtime
