Support

January 17, 2018 at 7:05 am

Hi Lawrence,

I took a quick look at your page and that page has a lot of ticket options, and each ticket option pulls quite a bit of data from the database. The page load can be sped up by reducing the number of queries to the database. One way to reduce the queries would be to remove each ticket’s show details section. That can be done by going to Event Espresso > Events > Templates, then set the “Show Ticket Details?” option to No.

Then you could also try caching that page with an Azure compatible caching plugin. Caching will also speed up the page because instead of querying the database every time someone requests the page, it will serve a cached file.

January 17, 2018 at 5:00 pm

Obviously I have turned it off as instructed

It doesn’t look like you turned off the show details option. Are you sure that you’re editing the settings for that site? Maybe you made edits to the https://www.thebrownstoneny.org/ site’s settings?

January 18, 2018 at 1:30 pm

You can also try caching that page with an Azure compatible caching plugin. Caching will also speed up the page because instead of querying the database every time someone requests the page, it will serve a cached file.

January 22, 2018 at 2:11 pm

No, please do not compact or remove data from the database. I mentioned earlier, twice, about caching. Can you not cache the page so PHP doesn’t have to generate it with every request?

January 22, 2018 at 2:25 pm

That page isn’t being served from a cache. When WP Super Cache serves a page from the cache, it leaves a little html comment near the bottom of the page source like this:

<!-- Dynamic page generated in 7.422 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2018-01-22 16:23:38 -->

<!-- super cache -->

Nothing like the above is present within the source of that page.

January 23, 2018 at 8:53 am

One thing about WP Super Cache is it has settings to configure it to serve cached file to known users or not. Which may be why it’s faster sometimes and then not.

While caching can help, if the underlying issue is the server has some opportunities for tuning for better performance then that will require some more information which can involve these 3 points:

1. What are the specifications of the environment? e.g. how much CPU, how much Ram? What is the database?
2. You can install a plugin like QueryMonitor to see what are the slow queries for that page and that could provide some next steps for troubleshooting
3. You may want to consider adding a monitoring service such as New Relic to your server to help identify bottlenecks in the code running on your site and server. That will shed some insight into where improvements can be made. Event Espresso runs New Relic for its various sites and we use that to help improve EE’s sites in numerous ways to reduce its impact on member’s sites. Every environment is different though, so we appreciate learning from other customers on various platforms with actionable measurements.

For what it’s worth, Event Espresso uses a standard Digital Ocean droplet to host its demo site (which is a Multisite network of 170 demo sites). Here’s an example demo site with a similar amount of tickets, can you see that it has no trouble with loading the page?

http://demoee.org/campout/events/campout-east/