Initial sync of the calendar takes a prohibitive amount of time

Bug #1339016 reported by Pat McGowan
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
Unassigned
sync-monitor
Fix Released
Critical
Renato Araujo Oliveira Filho
sync-monitor (Ubuntu)
Fix Released
Critical
Unassigned
sync-monitor (Ubuntu RTM)
Fix Released
Critical
Renato Araujo Oliveira Filho
syncevolution (Ubuntu)
Fix Released
Critical
Unassigned
syncevolution (Ubuntu RTM)
Fix Released
Critical
Renato Araujo Oliveira Filho

Bug Description

Mako running 116

Initial sync of default google calendar ran continuously for 90 mins before I terminated it
The ics file grew to 8MB

I can see two major things from the log:
- it syncs all past events (I would suggest starting with the current or previous month if necessary)
- it adds recurring events repeatedly (is the query using the wrong API and receiving events by timeframe rather than as raw event data?)

Tags: ota-2 rtm14 ww07

Related branches

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :
Bill Filler (bfiller)
tags: removed: rtm14
Bill Filler (bfiller)
tags: added: rtm14
Revision history for this message
Bill Filler (bfiller) wrote :

see related bug about memory usage by evolution-calendar-factory:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1342123

Revision history for this message
Bill Filler (bfiller) wrote :

We use syncevolution, which communicates with Google on the remote side and evolution-data-server on the local side to store events. There is no API in syncevolution to limit the scope of events retrieved. We need to look into modifying it to do so, and to optimize it's operational time as it's ridiculously slow (this in part is likely due to evolution-calendar-factory using a flat file to store the calendar events).

Renato has indicated there is a newer version of syncevolution which has recently been released that may improve the situation. The next step is to try this new version and see if it helps.

Revision history for this message
Victor Tuson Palau (vtuson) wrote :

Can we look at the new version so we can better evaluate the options to fix it

Bill Filler (bfiller)
tags: added: touch-2014-10-02
Bill Filler (bfiller)
tags: added: touch-2014-10-30
removed: touch-2014-10-02
Bill Filler (bfiller)
Changed in sync-monitor:
status: New → Confirmed
Changed in evolution-data-server (Ubuntu):
status: New → Confirmed
Changed in syncevolution (Ubuntu):
status: New → Confirmed
Bill Filler (bfiller)
tags: added: touch-2014-11-16
removed: touch-2014-10-30
Joe Odukoya (jodukoya)
tags: added: ota-2
removed: touch-2014-11-16
Bill Filler (bfiller)
no longer affects: evolution-data-server (Ubuntu)
Changed in sync-monitor (Ubuntu):
status: New → Fix Committed
importance: Undecided → Critical
Changed in syncevolution (Ubuntu):
status: Confirmed → Fix Released
importance: Undecided → Critical
Changed in syncevolution (Ubuntu RTM):
importance: Undecided → Critical
Changed in sync-monitor (Ubuntu RTM):
importance: Undecided → Critical
Changed in sync-monitor:
status: Confirmed → Fix Committed
Revision history for this message
Bill Filler (bfiller) wrote :

We were able to improve the situation by limiting how far in the past to sync for calendar events. This was a combination of a new version of syncevolution, and a patch to it and sync-monitor to introduce a "syncInterval" configuration setting (defaults to 90 days) specifiying how many days in the past to go back when syncing. For my caledar, it used to take 20 minutes for initial sync. Now it takes 33 seconds! Will need testing by others but this seems to help greatly.

Bill Filler (bfiller)
tags: added: ww03
Changed in syncevolution (Ubuntu RTM):
status: New → In Progress
assignee: nobody → Renato Araujo Oliveira Filho (renatofilho)
Changed in sync-monitor (Ubuntu RTM):
status: New → In Progress
assignee: nobody → Renato Araujo Oliveira Filho (renatofilho)
Changed in canonical-devices-system-image:
importance: Undecided → High
milestone: none → ww05-2015
status: New → Confirmed
Bill Filler (bfiller)
tags: added: ww05
removed: ww03
Bill Filler (bfiller)
tags: added: ww07
removed: ww05
Changed in canonical-devices-system-image:
status: Confirmed → In Progress
milestone: ww05-2015 → ww07-2015
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Add to critical per product team

Changed in canonical-devices-system-image:
importance: High → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sync-monitor - 0.1+15.04.20150127~rtm-0ubuntu1

---------------
sync-monitor (0.1+15.04.20150127~rtm-0ubuntu1) 14.09; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Renato Araujo Oliveira Filho ]
  * Use the new "startDate" filter to limit the number of events
    retrieved on the first calendar sync. (LP: #1339016)
 -- Ubuntu daily release <email address hidden> Tue, 27 Jan 2015 13:43:48 +0000

Changed in sync-monitor (Ubuntu RTM):
status: In Progress → Fix Released
Changed in canonical-devices-system-image:
status: In Progress → Fix Released
Changed in sync-monitor:
status: Fix Committed → Fix Released
Changed in sync-monitor (Ubuntu):
status: Fix Committed → Fix Released
Changed in syncevolution (Ubuntu RTM):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.