|
Keith Portman
|
July 24, 2013 at 4:04 pm
I’m currently using EE to help an after-school program organization setup event registration for 400 schools across the country. Each school will have 1-2 programs each, running 13 days for half of the school year. Each program has between 5-35 students.
Currently i have my website setup with multi-site WordPress. One site runs event registration, one runs the staff portal, and one runs a franchise page. I might consider using other sites, AND i’m also considering setting up 8 separate event registration sites for each region we have schools in. This way, events and all info for each region will have their own section.
Here are my basic questions:
1) Will setting up sites per region significantly improve site performance/speed, particularly on days with high-traffic registration (the first couple weeks before and after programs begin)?
2a) Will giving these individual regions their own individual sites allow for better performance over time? If i kept all event registration on one site (for all regions), there will be approximately 1000 programs per year, each having 13-days per program, or 13000 events per year. Is separating by region gonna help my site performance over time, or should i keep everything together on one site?
2b) Elaborating on the last question…..Will having this many events/attendees prohibit my site from working altogether, whether or not each region has it’s own site on multi-site wordpress.
NOTE: I’m running on SSD Liquidweb Servers with 6GB ram and 2 CPUs, so performance has been pretty impressive on my test-site so far. Concerned if it will keep going after a couple years of thousands of events and attendees.
Love EE! Thanks in advance for any recommendations!
|
|
Josh
|
July 24, 2013 at 5:07 pm
Hi Keith,
While we haven’t tested out multi-site vs single-site to see if there are performance differences, what you are suggesting about separating these into smaller more manageable chunks makes sense. From a admin point of view it’s a lot fewer events to sort through when the regions are organized into their own sites.
It sounds like you have the right server set up to handle a large amount of events. To be honest, Event Espresso will only query up 500 events at a time in the admin at a maximum, the next 500 can be queried by hitting the next button in the event overview.
|
|
Keith Portman
|
July 24, 2013 at 5:32 pm
Thanks for the quick reply Josh.
So, essentially, you’re saying i have no choice but to separate by region, correct?
If what i think you’re saying is correct, each region would only be able to handle 500 events in the database. So, the entire multi-site would be allowed to handle well more than 500 events combined, but only 500 per site/region. Correct?
Thanks again for your help!
|
|
Josh
|
July 25, 2013 at 6:56 am
You do have a choice, while you could go with one site for all the regions, I would lean towards breaking the venues up in to smaller more manageable sites.
One reason: While Event Espresso does handle more than 500 events, and it will even try to load all of them up if you select all. This is the next option after pulling up 500 events. What I’m trying to say is when you go from 500 to All and you’re trying to load up 13,000 events it could time out when it tries to load up 13,000 events, or at best load up but slow down the admin as it’s trying to load up all those records. So using the “retrieve 500 events from the database at a time” feature would be another way to go. If the event you’re looking for is #12245, you can still access it, but it would require retrieving all -or- skipping through ~ 25 pages that have 500 events each.
|
