Closed Bug 1758639 Opened 4 years ago Closed 3 years ago

Latency when adding events using remote calendar

Categories

(Calendar :: Calendar Frontend, defect)

Product:
Calendar
Component:
Calendar Frontend
Version:
Thunderbird 91
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: adrien.rybarczyk, Unassigned)

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.102 Safari/537.36

Steps to reproduce:

  1. Have a remote calendar
  2. Be online
  3. Have a certain amount of events on the calendar
  4. Add events

Other possible experience is to go offline to add a dozen events and go back online. It will resynchronize the calendar at each addition and it could have been improved by refreshing at the end of the operations. When testing this, the user can wait about 20 seconds, if he has a substantial agenda on the current view, before being able to do something.

Actual results:

The calendar is very slow. Refreshing the calendar, for calendars with many events, can take several seconds, which isn't great when you move / add an event and have to wait this time before it actually ends refreshing.

Expected results:

This complete synchronization every time is a good idea to keep the calendar updated. But there is already the possibility of automatic synchronization every X minutes.
For people who create a lot of events, but are not invited much, this synchronization is annoying.

In this case, at worst propose an option in the calendars to ask if the user wants to synchronize all his calendar at each modification he makes.

Keywords: dupeme, perf

I wonder what we could do here. Could we optimistically add the event to the calendar, and only do the sync after that? Maybe keep some flag on the event noting it's still in flux?

Summary: Latency when using remote calendar → Latency when adding events using remote calendar

I indicated by adding but there is the same problem if you modify an event.

Maybe make a synchronization just on the modified or added event.

In Beta version, the behavior has been modified and the problem is solved. There is no more the refresh of the whole interface at each modification which gives this slowness in 91.

Alright, let's close then.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.