Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Hosting Requirement Specs? | Event Espresso - Staging Server
We are hosted with Namesecure and our site is running super slow. Sometimes we are having database connection issues. We are talking to Namesecure to upgrade our service level, and they need to know what our system requirements are. What is suggested to run Event Espresso at a decent speed? Average 35-45 visitors per day, peaked at 60 visitors per day. Hourly average peak is 3 per hour, max peak was 10 per hour.
It will list out some recommendations. The Event Espresso>System Status page will try to detect your server’s settings and also list out recommendations (like minimum amount of memory to at least 64MB).
Another thing to consider is you can make some performance changes to the site that are independent from increasing the amount of resources available. Here is one guide that I’ve found helpful:
Please note, if you install a caching plugin like WP super cache, you will need to exclude the Event Espresso pages from the page cache, which can be done in the WP super cache advanced settings.
The requirements plugin does not work for some reason. The current level we have with namesecure can barely process wordpress on its own. The database is also frequently unresponsive. I think they need to be told explicit CPU and Database req’s?
You might see if you can get a virtual dedicated host account from them. The issue may be number of shared hosting accounts on the same server.
Viewing 5 reply threads
The support post ‘Hosting Requirement Specs?’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.