726428 - Poor response time when completing or snoozing a recurring task

Status: RESOLVED DUPLICATE of bug 362987

(Calendar :: Tasks, defect)

Description

[Mark McClain]

User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.46 Safari/535.11

Steps to reproduce:

Either of these acts results in poor response time before completion (applies only to tasks that are recurring): 1) checking the completion box on the task list, 2) snoozing the task in the reminder screen.


Actual results:

Response time is consistently about 15 seconds during which time no other action can be done. Tasks that are not recurring normally clear in about 1-2 seconds.


Expected results:

Either figure out why this job takes so long and fix that, OR find a way to do this in the background (maybe put a check in the box to let user know it's being processed) and allow other actions to be done by the user.

Comment 1

[Matthew Mecca [:mmecca]]

What type of calendar are you using?

Comment 2

[Mark McClain]

Lighting 1.2.1 addon to Thunderbird 10.0

Comment 3

[Matthew Mecca [:mmecca]]

Is this a local storage calendar on your computer, a local .ics file, or a network calendar you're subscribed to using WebDAV or CalDAV?

Comment 4

[Mark McClain]

It is a local storage calendar on my computer.

Comment 5

[Mark McClain]

When I go to the Thunderbird data folder, there is a folder called calendar-data/backup that contains .ics files with last modify dates around the time I first installed this program (Nov. 2011).

Comment 6

[Matthew Mecca [:mmecca]]

Confirming. When an occurrence of a repeating task is completed, an exception is created that saves the properties of that occurrence including the status and completion date. The storage provider takes around 50 ms longer per exception on my machine to record a modification, which can add up to seconds over time, especially with daily repeating tasks.

One workaround to improve performance is to periodically delete old completed occurrences, or even better to delete the entire series of a repeating task and re-create it with a current starting date.

I think there are a few things we can do to improve performance:
- We currently trigger a full refresh of the task trees when a repeating task is modified, which adds to the time before the display is updated.
- I like the idea of updating the check box display before the transaction is processed.

Comment 7

[Mark McClain]

Thanks for the idea on workaround. You're right, culprit is daily occurring task which can easily be deleted and reentered when performance is affected, and can periodically delete all completed tasks. Obvious improvement would be to have a parm for automatically deleted completed tasks after x days.