Support

February 11, 2019 at 5:22 am

Hi Jeremy,

As you correctly mentioned, it all depends on your server, however, your question seems to contradict itself a little, so to clarify:

I’m not referring to limiting the number of tickets that a user can book, but the total number of registrations that can safely be created simultaneously in EE.

Then:

For instance, I’ve just tried to make a booking with 100 places – with a 6 question registration form, and only collecting data from the primary registrant – and it’s caused the page to crash.

Unless I’m misunderstanding, you are referring to the number of tickets a user can purchase in a single instance?

I’m guessing the crash you had was after 30 seconds from when you submitted the selection? The reason I say that is 30 seconds is the default max_execution_time value when you install PHP and that’s what most host’s leave it as. Meaning you submitted the tickets and it took longer than 30 seconds for the server to create the 100 registrations, so the script was killed, you can confirm this by looking in the error logs and looking for a max_execution_time error (or retest with WP_DEBUG enabled and the error should show on the page itself).

There’s not enough info above to know if that’s the actual cause, just an educated guess.

I know that the server and allocated memory will factor heavily into this, but I just wanted to know if there was a tested limit that I should try to keep within?

No, because each case is different.

To explain a little there is a 1-to-1 relationship between tickets and registrations. When you select a ticket within EE a registration is created for that ticket when you submit the ticket selector, meaning if you select 100 tickets, 100 registrations are created.

I have multiple test sites across various different hosting packages and as an example on a cheap shared hosting package ($3 a month) I have no problem creating 100 registrations in a single step, it takes a little longer than a request with fewer registrations but still within 30 seconds (Avg of 19 seconds).

However, would I get the same results during a registration season with multiple various visitors submitting 100 registrations at once, likey not and the config would need to be tweaked to handles that so there is no clear cut answer.

May I ask what use case this is for?

What type of hosting are you using?

February 11, 2019 at 9:29 am

Hi Scott,

We’ve received your request for priority support. I logged in to the site, and the number 1 item I can recommend is ask the web host to update to PHP 7.2 or greater. Currently the site is on PHP 5.5, which reached end of life in July 2016. The newer versions of PHP are much more performant. Here’s a quick reference that shows some simple benchmarks, for example:

https://gbksoft.com/blog/php-5-vs-php-7-performance-comparison/#vpv4A

February 13, 2019 at 4:15 am

Updating PHP is going to have the biggest improvement on speed.

If you’re expecting to run registrations with large ticket qty’s on each purchase you’ll want to make sure you have enough memory available, running on the bare minimum isn’t going to cut it. As if you have multiple users purchasing large qty’s of registration at the same time you’ll use more memory.

What type of hosting are you using? Is it shared?

If so you’ll likely want to look at switching to something a little more substantial, otherwise, you may run into issues when other sites are under load on the same server.

February 18, 2019 at 8:14 am

Just noting here that we received your support token request and have replied via email.