|
ndaniel
|
September 21, 2012 at 6:28 am
Version: 3.1.27 We currently have 430+ events and 2,850+ attendees in the system. The performance of the event and attendee screens is degrading as the volume of data increases. This is over https, which I have seen you mention as a concern, but it does seem the volume is the measurable concern, not the protocol. There have been no changes made to the hosting configuration. The performance was fine when volume was lower, perhaps 25% ago. Any suggestions on optimization for performance? This is becoming a true administrative burden. Other site features are responding well, including other EE pages.
Error on All Attendees page: Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
Cheers, Bill
-
This topic was modified 4 years, 1 month ago by
 Garth.
|
|
Seth Shoultes
|
September 21, 2012 at 8:24 am
Bill,
Thanks for letting us know. We have already begun working on the issue earlier this week. We should have the optimizations ready for testing very soon.
|
|
ndaniel
|
September 28, 2012 at 5:21 pm
Seth, thanks.
I can provide an export of my database for your use in testing if you like.
I am concerned that as we add more events and customer records the system will degrade in other areas. Are the optimizations you mention going to be prioritized in 3.1 or 3.2? It seems we’re not the first to encounter the issue.
A straight forward work around may be to by-pass the initial bulk collection of data on the initial event admin screens. Forcing filters to be set.
I really need the all attendees screen, but haven’t been able to use it for some time now – this is the error:
Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
I am inclined to delete attendee records in an incomplete status to try and lighten the load. If users go “back” to modify their registration form, there are duplicate attendee records created. I think this is an known issue based on past posts.
I have installed ELI’s Custom SQL Reports to meet the daily need for now, but I would rather use the built-in features of EE. The only other option I can think of would be to export old records into another database and delete those archived records from EE. Clearly that is a last resort aside from moving to a system that better handles our volume.
I want to minimize any back-end administration so the admin users of EE don’t need to rely on me for advanced support so much. By the end of next week, we’ll need to about add another 150 events, putting us near 600, so there is a sense of urgency for us.
Thanks,
Bill
|
|
Seth Shoultes
|
September 28, 2012 at 6:09 pm
Hi Bill,
We are almost done with a huge optimization for 3.1.28. I actually pulled one of the developers working on 3.2, off to focus on 3.1. We should be close to testing 3.1.28 on or around October 1st. He has made major improvements over the last 2 weeks.
|
|
ndaniel
|
October 2, 2012 at 4:13 pm
Seth,
Thank you & your team for the prompt replies. Do you anticipate 3.1.28 release soon? I need to start adding nearly 200 more events now and will take all the optimizations I can get before I start!
Cheers,
Bill
|
|
Seth Shoultes
|
October 2, 2012 at 6:54 pm
Myself and one of the developers spent the entire day testing and debugging the latest major changes today. I am truly hoping we can get it released by next week.
|
|
ndaniel
|
October 9, 2012 at 8:28 pm
Hi Seth,
Just wondering if you have a status update on 3.1.28?
Do you consider that release a fix for the inability to pull up the All Attendees page and other apparent performance issues?
Best regards,
Bill
|
|
Chris Reynolds
|
October 10, 2012 at 11:56 am
Hi Bill —
I don’t think anyone can say for sure if the update will fix your specific problems short of testing it on your server. That said, it’s not going to hurt and any potential database issues — even little ones here and there — get exponentially more dramatic the more database calls are made. If optimizations have been made and individual database calls have been reduced (which they have), it should improve performance overall, but we can’t guarantee that it would be a fix for your All Attendees page issue, specifically.
|
|
ndaniel
|
October 14, 2012 at 12:10 pm
Has anyone else reported a problem with viewing the All Attendees screen up?
Is this a data volume issue? No attendee data has been put into the system aside from EE GUI entry either by registrants or by admins. This issue is rendering a valuable part of the tool completely useless and exporting the data every time we need to review a customers history is not very fun.
Thanks for any insight you can offer.
|
|
Josh
|
October 15, 2012 at 1:06 pm
Yes, someone had, and they turned off SSL for the admin pages and it worked after they did that.
|
|
ndaniel
|
October 15, 2012 at 1:20 pm
Thanks Josh. Can you advise on how to turn off SSL for only the admin pages? I’m not seeing that option, so I guess I’m missing something obvious.
|
|
Josh
|
October 15, 2012 at 1:41 pm
It’s not a feature that Event Espresso adds. I’m aware of two methods to force SSL on admin pages: editing the wp-config.php file -or- a using plugin like WordPress Https.
|
|
ndaniel
|
October 15, 2012 at 3:03 pm
Thanks Josh. Unsetting SSL on the admin pages didn’t turn the trick. Looks like this can result from a few areas with WordPress. If I find the answer, I will share.
Thanks,
Bill
|
|
ndaniel
|
October 15, 2012 at 7:49 pm
In review, I should have been more clear about the “All Attendees” issue. It works for the “Today” (77 results) and “This Month” (585 results) query, but not for the all history option (2660 results).
After researching this all day, and trying various options of tuning plugins, etc, I can only conclude this is a result of the nature of the query.
My first suggestion would be dropping EE admins into filter options prior to generating the query. I would suggest the same for the All Events option. Our prior event system had over 7,000 entries (same server/hosting/MySql platform, etc) and we will hit that mark after the holidays in EE. As you collect customers with this quality event management tool, everyone will be glad for starting with filters and not allowing unqualified queries.
Cheers,
Bill
|
