I appreciate the suggestion, but neither of those are a great fit for us. I'm sure Varnish is up to the task of handling our relatively plain usage case. It's likely some sort of configuration error on our part, so I'd love to have eyes and ears on that gist I provided with our current setup.
On Mon, Oct 20, 2014 at 5:06 PM, Tobias Eichelbrönner < [email protected]> wrote: > Hi Greg, > > > To help withstand some bursty traffic from one of our customers, we > > worked Varnish in behind ELB > > > If we yank Varnish out, the problem goes away immediately. Here's what > > our varnish config looks like atm: > > We experienced trouble sending traffic bursts to ELB in the past. I > would suggest putting a simple nginx for SSL termination in front of the > Varnish and try to leave the ELB out. If one instance cannot handle the > traffic, mybe DNS round-robin is a solution. > > Sincerely, > > Tobias > > -- > LAMP solutions GmbH > Gostenhofer Hauptstrasse 35 > 90443 Nuernberg > > Amtsgericht Nuernberg: HRB 22366 > Geschaeftsfuehrer: Heiko Schubert > > Es gelten unsere allgemeinen Geschaeftsbedingungen. > http://www.lamp-solutions.de/agbs/ > > Telefon : 0911 / 376 516 0 > Fax : 0911 / 376 516 11 > E-Mail : [email protected] > Web : www.lamp-solutions.de > Facebook : http://www.facebook.com/LAMPsolutions > Twitter : http://twitter.com/#!/lampsolutions > > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc > -- Greg Taylor, Pathwright Co-founder http://www.pathwright.com (864) 334-8735
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
