|
anthroarts
|
January 21, 2015 at 11:22 pm
Hi folks!
So we had a successful year running EE for our registrations, however now I can’t seem to get a CSV output. We have roughly 3500 registrations, and 8 possible questions. I know this is a huge query.
I’ve attempted to raise the memory limit and the execution time limit for PHP, but no matter what I do, I seem to get the same error. I’ve updated /etc/php5/apache2/php.ini, as well as put ini_set values in wp-config.php, neither seem to have any effect. I’ve tried raising the limit up to 4096M (the server has 4GB RAM and 2GB Swap) and even tried setting the limit on both to -1.
Every time the error pops up the same:
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /var/www/reg.furcon.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2573, referer: https://reg.furtherconfusion.org/wp-admin/admin.php?page=espresso_registrations&action=default&event_id=10&default_nonce=
Any ideas? This error seems to suggest that the server still wants to limit to 256MB, even with the config changes (and apache restarts) in place.
|
|
Josh
|
January 22, 2015 at 7:35 am
Hi there,
One idea that you can try is you break that query up into smaller chunks. Here’s a link to a related thread that explains how:
https://eventespresso.com/topic/csv-report-download-problem/#post-119066
|
|
anthroarts
|
January 22, 2015 at 9:28 am
I had found that post, and I might use that as a stop-gap, though I’d like to solve the underlying problem of why memory usage is locked. We’re going to need to be able to generate these reports fairly regularly, and as our event grows, we’re going to have larger datasets. Altering the code to get 100-500 attendee chunks every time, and doing this whole process on a weekly basis isn’t really scalable. I’m okay with throwing memory at the problem, but I’d like to figure out how. 🙂
|
|
Lorenzo Orlando Caum
|
January 22, 2015 at 11:12 am
Hi there, I wanted to add that were are investigating a batching option for export which should help with this issue.
Also, the queries in the next major release of Event Espresso 4 are more efficient so that should also help.
In your support post, you mention that you are on an older version of Event Espresso 4 at 4.2.7.
Could you please backup your WordPress and update to the current release of Event Espresso 4?
You can view changes since your version here:
https://eventespresso.com/wiki/ee4-changelog/#4.2.7
—
Lorenzo
|
|
Lorenzo Orlando Caum
|
December 31, 2015 at 12:19 pm
Hello,
A current version of Event Espresso 4 introduces a batching feature where the records are retrieved in the background and then combined into one file. This will help with events with thousands of events.
You can see the changelog here:
https://eventespresso.com/wiki/ee4-changelog/
Be sure to backup your WordPress site (https://eventespresso.com/wiki/how-to-back-up-your-site/) before making changes.
If you have any other questions about Event Espresso 4, then please create a new support post in our support forums:
https://eventespresso.com/support/forums/
Thanks and have a happy new year!
—
Lorenzo
|
