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 5, 12:00 pm, Chris Hanks <[email protected]> wrote: > Is anyone from Heroku around that might know how their setup works? > > On Oct 2, 8:42 pm, Chris Hanks <[email protected]> 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. Right after Varnish's copy expires, if it's very > > popular, I might have a dozen people accessing it simultaneously > > before the newly created version can be stashed in Varnish. > > > So, based on a thread I found (http://www.gossamer-threads.com/lists/ > > varnish/misc/14750) it looks like Varnish is smart enough by default > > to only send that expensive request to my backend once, and serve up > > the response to all the people waiting for it (to prevent a dogpiling > > effect). But I know that Heroku has its own configuration for Varnish > > (with lots of servers in a hash ring), and I was wondering whether > > it's still set up to do this. > > > Thanks! -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
