1581294 - Google network calendar with ~4000 items takes ~8mn to load - lightning/calendar 68.1 - Provider for Google Calendar 68.1 (gdata-provider) - Thunderbird 68.1 ESR

Status: RESOLVED INVALID

(Calendar :: General, defect)

Description

[Richard Leger]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Following performance issues reported with CalDav network calendar in Bug 1502923 and Bug 1572823 (Work in Progress), I thought to take the same approach to measure performance and evaluate progress over time of loading Google Calendar with ~4000 items via Lightning/Calendar and Provider for Google Calendar (gdata-provider).

Environment setup steps:

• Install Thunderbird 68.1 ESR (British version) from https://download-installer.cdn.mozilla.net/pub/thunderbird/releases/68.1.0/win32/en-GB/Thunderbird%20Setup%2068.1.0.exe
• Create a new Thunderbird user profile
• No email setup
• Go to TB Menu > Add-ons > Extensions
• Search for Provider for Google Calendar
• Add this add-on via the add button
• Restart Thunderbird
• Set to show All Events in Find Events view (unifinder)
• No columns selected in Find Events view (default settings)
• Add one Google network calendar with ~4000 items

Actual results:

• Loading the entire calendar takes more than 8 minutes!

Expected results:

• Loading such calendar via .ics file over HTTP takes only 1 or 2 seconds max!

Comment 1

[Richard Leger]

Attachment: devtools.network.jpg

Philipp,

Any advise on how loading speed of Google Calendar can be improved in Thunderbird 68.1 ESR?
Any setting tweaks available to end-users?

It take 2mn loading per 1000 items batch in Thunderbird lightning/calendar UI...

Is that related to Bug 501689 you refer to in Bug 1544320 Comment 35?

Comparatively network wise (DevTools > Network) the situation is much better with Google network calendar than with CalDAV network calendar (as per Bug 1543953):

ADSL - All Events - No sorting (unifinder) - One Google calendar with ~4000items

#	TB Version	LoadingTime	DevTools > Networking
1	'''68.1.0''' (32-bit) ESR	'''~8m02s'''	'''6 Requests''' - 4.17MB Transferred - Finish: 6m65s

Regards,

Comment 2

[Jorg K (CEST = GMT+2)]

Looks like the Calendar::Provider:GDAta was removed from BMO. Please report all issues for this 3rd-party add-on at https://github.com/kewisch/gdata-provider. We're in the process of removing it from the comm-central repository.

And in general: Please try to report bug in the correct product/component.

Comment 3

[Richard Leger]

Jorg,

This is quite a surprising move... what it the logic behind it?

On one hand Lightning and CaldDAV network calendar is being integrated as core feature of Thunderbird with all bugs handled via BMO, on the other hand Calendar::Provider:GDAta is being remove from comm-central and bugs issue no longer handled via BMO? This is quite confusing...

Ability for Thunderbird to sync network calendar seamlessly should be a core feature of Thunderbird... disregarding providers...

Regards,

Comment 4

[Richard Leger]

(In reply to Jorg K (GMT+2) (reduced availability 14-19 of Sept.) from comment #2)

Looks like the Calendar::Provider:GDAta was removed from BMO. Please report all issues for this 3rd-party add-on at https://github.com/kewisch/gdata-provider.

Issue has been re-opened on GitHub here:
https://github.com/kewisch/gdata-provider/issues/14

Comment 5

[Richard Leger]

(In reply to Jorg K (GMT+2) (reduced availability 14-19 of Sept.) from comment #2)

Looks like the Calendar::Provider:GDAta was removed from BMO. Please report all issues for this 3rd-party add-on at https://github.com/kewisch/gdata-provider. We're in the process of removing it from the comm-central repository.

Jorg,

You may want to update the https://wiki.mozilla.org/Calendar:GDATA_Provider with the information above as on the wiki it still indicates to report Gdata-Provider issue via BMO...

Regards,

Comment 6

[Jorg K (CEST = GMT+2)]

This development is new and still in flux. I think the logic behind this is that the TB team are focusing on supporting open protocols, like CalDAV, while proprietary protocols are left to add-ons. There is a bit of discussion in bug 1570933. There will be a tb-planning announcement soon.