I’m expecting 700+ concurrent users for a brief 2-3 hour window. I feel like I’ve been getting conflicting info from pantheon: an agency partner rep says that the site will elastically spin up new containers to accommodate traffic spikes; previous interactions with support have told me that I will NOT get any additional php workers and that, therefore, my site will likely choke and die. Can I get a solid answer here? Do I need to crank up my plan or not? It’s a one-time event; most of the year the site receives relatively little traffic.
Some details:
-
FWIW this is a woocommerce site, and much of the traffic will bypass varnish/the caching layer.
-
The spike is caused by a first-come-first-serve event ticket release at 5am, which is not a super great idea to begin with, but it’s what it is.
-
Yes, I have done as much performance tuning and tweaking as is reasonably possible without digging into woocommerce internals or rewriting woocommerce plugins.
-
Yes, I have been using blazemeter to load-test my test environment with the understanding that the test environment has two php workers, and the live environments on larger plans will have more.
-
Yes, I have been using new relic to isolate performance bottlenecks.
-
Right now the site is a performance small.
Any tips or advice? Do I need to upgrade to a larger plan in order to get better performance or not?