Performance issue with many clients/users

[sebasi]

I am evaluating this application and already did many changes so it fits my needs. Nicely done, I felt at home quite fast. :)

I got a bit scared when I saw that all customers are serialized into javascript when loading the backend/customers page and when creating a new appointment via the backend.

This works of course nicely for a couple of customers, but a quick sql insert in mysql that generated 10.000 users (with role 3) showed that loading backend/customers takes about 10-20 s (on my virtual test system).

Is this a known issue? I couldn't find a ticket or comment in the google group. I think it's not trivial to change that as e.g. the search also relies on this data. Ideally this data would not be loaded by default and the search would be executed on the server and only matches would be loaded.

@alextselegidis I can imagine you are quite busy, but I would like to hear thoughts on this. I know that I am going to run into this issue.

Viele Grüße nach Bremen, Sebastian

[alextselegidis]

Hello Sebastian,

thanks for posting here. This is is a known issue and I was thinking of integrating a lazy loading mechanism or even do some pagination as no back-end user will need all the customer records at once.

Being said I didn't find the time to do this till now but feel free to make a pull request if you come up with a solution :)

LG Alex

Alex Tselegidis, Easy!Appointments Creator   Need a customization? Contact me in person!

[mynameisjonas]

Hi Alex,

Appreciate that you are probably busy, but just wondered whether you had any plans to work on this for an upcoming release? I have a production deployment with ~700 customers and 4000+ appointments and have noticed that clicking on Customers in the backend and executing ajax_filter_customers is now taking ~25seconds to execute. From my test instance I can see this time increases with the number of appointments so assume loading time is going to increase over the coming year as customers continue to book appointments.

Thanks Nick