|
Sydney
|
May 8, 2017 at 11:14 am
We have been running the iPad EE app. Having multiple events and or large numbers of attendees causes the app to run really slow (it also massively spikes the cpu usage on our webserver). Considering our ticket and event databases are small (<10mb) this seems to indicate the problem is with the app. It appears to download a lot of extra data but am not yet sure what.
|
|
Sydney
|
May 8, 2017 at 11:45 am
Also we are now getting the following error when trying to sign in to the app on new devices:
“Connection error. Unable to load data”
|
|
Josh
|
May 8, 2017 at 1:07 pm
Hi there,
You’ll need to make sure you have the current version of the iOS and/or Android apps, and you can follow this troubleshooting guide:
https://eventespresso.com/wiki/ee4-event-apps/#troubleshooting
It may also help to rule out any plugins that interact with the WordPress REST API in case any are filtering the API requests.
|
|
Sydney
|
May 8, 2017 at 1:11 pm
I have followed those steps and also run the site without any plugins (other than ee) active and still have the problem. It appears to me to be a scaling issue with the app. once there are a a few hundred tickets spread across a few dozen events it starts to grind to a halt. Increasing hosting resources does not seem to improve this.
|
|
Josh
|
May 8, 2017 at 1:30 pm
We have not seen this happen on other sites with more than a few hundred tickets and more than a few dozen events. You mentioned the hosting resources, is that on a VPS?
|
|
Sydney
|
May 8, 2017 at 5:32 pm
we are noticing performance issues for events with large numbers of event datetimes too so definitely think something isnt scaling linearly.
|
|
Josh
|
May 9, 2017 at 6:44 am
That’s not what we’ve seen with testing. You can log the queries by using the WP REST API log plugin and see the queries the that are made by the apps.
|
|
Sydney
|
May 10, 2017 at 3:16 pm
With only EE4 plugins enabled an attempt to log on from a new device gives
‘Connection error. Unable to load data’
The rest log shows the request also:
Elapsed Time: 56,545ms
Response Length: 295,759
which seems excessive given that the response body is only 289KB
|
|
Josh
|
May 11, 2017 at 9:08 am
Are those requests going directly to your server or is there an intermediary where the request gets forwarded to? Like for example is cloudflare set up for the domain?
|
