|
Darel Parker
|
February 3, 2015 at 8:21 pm
We’ve been using Event Espresso successfully for several months on small events with 100 to 200 tickets per event. We now have an opportunity to provide ticketing services for an arena headliner with radio promotion and projected sales of 5000+ e-tickets. Based on similar events, we expect to sell out within an hour, possibly sooner if the server can handle the transaction volume. However, we have no frame of reference for anywhere near that volume on our server.
The big question is can Event Espresso manage this workload with the proper resources? If so, what would be the suggested minimum server configuration to process 80-100 ticket sales per minute?
Our website: http://www.rgvlive.com/
Here are the current specs:
WordPress 4.1
Event Espresso 3.1.36.6.P
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (8 core)
16 GB RAM
CentOS 5.11
Apache 2.2.27
PHP 5.4.30
Zend Engine v2.4.0
|
|
Jonathan Wilson
|
February 4, 2015 at 1:22 pm
Hi Darel,
Congrats on that opportunity! That’s huge.
We aren’t able to answer your question definitely. This depends on several factors, including (but not limited to) the server environment, your theme, other plugins and their compatibility, your caching configuration. With the description you provided, we suggest having a VPS or dedicated server.
We have seen EE function well for large events like this, but each case is different.
Hope this helps. ?I’ll be happy to answer anymore questions you might have.
|
|
Darel Parker
|
February 12, 2015 at 9:59 pm
Thanks for the follow up, Jonathan. We’re running load tests on our server to get a better picture of our maximum capacity and concurrent transaction volume. Hopefully we’ll be able to move forward with this event.
|
|
Josh
|
February 16, 2015 at 9:39 am
Hi Darel,
I can also advise using an on-site payment gateway when there are high volume ticket sales. This is because on-site payment gateways will allow less time between the payment and payment notification to your server. It’s closer to an instant update versus sending the ticket buyer off to something like PayPal or Moneris where they pay, then are sent back. The amount of time that goes by to process an offsite payment can lead to overselling.
|
|
Darel Parker
|
February 16, 2015 at 4:38 pm
Thanks Josh. We’re currently using Stripe (forced SSL) as our primary gateway with PayPal as a secondary option. Stripe has given us very low latency, and we have the reservation time set to 15 minutes. So far, so good.
|
|
Garth
|
February 16, 2015 at 9:34 pm
Darel,
If I remember correctly, we did have a user who load tested 5000+ concurrent users and the results came back favorably. But like Jonathan mentioned, it does depend on the server configuration plus the theme, plugins, geography, etc.
Let us know the results and your particular website configuration, especially if you have any questions or suggestions.
|
