Rainloop - Cannot export vcard #118

New Issue

Closed

opened 2021-08-07 08:14:36 +02:00 by muppeth · 4 comments

muppeth commented

2021-08-07 08:14:36 +02:00

Owner

Looks like vcard export is broken. We need to investigate urgently specially that we will need it soon when migrating to Roundcube

muppeth added the

🤔️ Investigate

Urgent!

labels 2021-08-07 08:14:36 +02:00

meaz commented

2021-08-08 08:13:29 +02:00

Owner

csv export too

meaz commented

2021-08-08 13:48:36 +02:00

Owner

Looks like php process timesout while waiting for db. Try to beef mariadb and check for possible indexes we could add to lower the wait time

muppeth commented

2021-08-09 11:36:16 +02:00

Author

Owner

From what I noticed it takes about 3 seconds to display all 3264 contacts I have on my account (test account with some random contacts imported for testing long time ago).
When exporting contacts, rainloop looks up each contact individually:
SELECT * FROM rainloop_ab_properties WHERE id_contact = XXXX;. This also takes about 3 seconds. So if you have 66 pages of contacts, this will surely cause timeout on php and terminate the operation.
What I will try to do is to minimize the time it takes for the lookup. However seeing that rainloop will do lookup for each contact, even if fast it may still cause timeouts on some accounts that have a lot of contacts. We should check which user hast the most and for the time set the timeout on php side to it ${avarage_query_time} * ${amount_of_contacts. I will try to get the avarage_query_time lower.

From what I noticed it takes about 3 seconds to display all 3264 contacts I have on my account (test account with some random contacts imported for testing long time ago). When exporting contacts, rainloop looks up each contact individually: `SELECT * FROM rainloop_ab_properties WHERE id_contact = XXXX;`. This also takes about 3 seconds. So if you have 66 pages of contacts, this will surely cause timeout on php and terminate the operation. What I will try to do is to minimize the time it takes for the lookup. However seeing that rainloop will do lookup for each contact, even if fast it may still cause timeouts on some accounts that have a lot of contacts. We should check which user hast the most and for the time set the timeout on php side to it `${avarage_query_time} * ${amount_of_contacts`. I will try to get the `avarage_query_time` lower.