Hi Ben,
Thanks a lot for your answers!
I'm looking forward to reading you about the other thread.
Thanks!
Thomas.
On Wed, Oct 13, 2010 at 11:40 PM, Ben Scofield b...@heroku.com wrote:
Sorry for the delay! I finally talked to our Varnish expert, and he
confirmed that:
1) our configuration
Sorry for the delay! I finally talked to our Varnish expert, and he
confirmed that:
1) our configuration should not impede Varnish's default behavior (re:
the first question in this thread), and
2) your app's resource configuration (# of dynos, etc.) doesn't affect
how much traffic Varnish can
Thanks, Ben!
On Oct 13, 2:40 pm, Ben Scofield b...@heroku.com wrote:
Sorry for the delay! I finally talked to our Varnish expert, and he
confirmed that:
1) our configuration should not impede Varnish's default behavior (re:
the first question in this thread), and
2) your app's resource
Hi Ben,
Any update about this?
Thanks,
Thomas.
On Tue, Oct 5, 2010 at 8:33 PM, Thomas Balthazar gro...@suitmymind.com wrote:
Hello Ben,
I just read you were about to talk to the Varnish specialist at Heroku.
I would really appreciate if you took the time to help me to find the
answer to
Thanks for looking into this stuff, Ben.
On Oct 5, 11:33 am, Thomas Balthazar gro...@suitmymind.com wrote:
Hello Ben,
I just read you were about to talk to the Varnish specialist at Heroku.
I would really appreciate if you took the time to help me to find the
answer to those 2 unanswered
Is anyone from Heroku around that might know how their setup works?
On Oct 2, 8:42 pm, Chris Hanks christopher.m.ha...@gmail.com wrote:
I'm wondering about Heroku's use of Varnish. Suppose I have a page
that is expensive to produce (lots of database queries) but can be
cached in Varnish.
Hi Chris,
I just did some quick tests, and it looks like Varnish is behaving as
advertised -- expensive requests are only sent to the backend once.
I'm going to confirm those experimental results with someone who knows
more about the configuration, but you should be good to go.
Ben
On Oct 5,
Not sure why this didn't come through earlier, but:
I tried out a few experiments, and it looks like our setup doesn't
interfere with this default behavior. I'm going to talk to someone
with more intimate knowledge of our Varnish config to confirm that,
but so far it looks promising.
Ben
On Oct
Hello Ben,
I just read you were about to talk to the Varnish specialist at Heroku.
I would really appreciate if you took the time to help me to find the
answer to those 2 unanswered questions about Varnish and caching :
http://groups.google.com/group/heroku/browse_thread/thread/8e39658d53c53b7c
I'm wondering about Heroku's use of Varnish. Suppose I have a page
that is expensive to produce (lots of database queries) but can be
cached in Varnish. Right after Varnish's copy expires, if it's very
popular, I might have a dozen people accessing it simultaneously
before the newly created
10 matches
Mail list logo
