Activity log for bug #1362548

Date Who What changed Old value New value Message
2014-08-28 10:53:23 Nekhelesh Ramananthan bug added bug
2014-08-28 10:54:03 Nekhelesh Ramananthan description This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. Just to note that this is also noticeable in the calendar app.
2014-08-28 10:54:27 Nekhelesh Ramananthan bug task added qtorganizer5-eds (Ubuntu)
2014-11-07 18:20:41 Nekhelesh Ramananthan ubuntu-clock-app: milestone rtm postrtm
2015-05-18 21:33:22 Launchpad Janitor qtorganizer5-eds (Ubuntu): status New Confirmed
2015-06-02 15:16:38 Charles Kerr bug added subscriber Charles Kerr
2015-07-16 21:11:38 Bartosz Kosiorek description This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. Just to note that this is also noticeable in the calendar app. This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. Just to note that this is also noticeable in the calendar app. [COMMENT] Most propably it caused by U1DB database storage. Migration to local storage should resolve this issue.
2015-07-16 21:16:31 Bartosz Kosiorek description This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. Just to note that this is also noticeable in the calendar app. [COMMENT] Most propably it caused by U1DB database storage. Migration to local storage should resolve this issue. This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. Just to note that this is also noticeable in the calendar app.
2015-07-16 21:18:28 Bartosz Kosiorek summary Alarms take several seconds to save (~5seconds) which is quite long compared to existing solutions Migrate from EDS to dbus
2015-07-16 21:21:21 Bartosz Kosiorek description This is something I have noticed on several occasions that alarms take a long time (~5 seconds or higher to save). This issue isn't new and has been there for a while. Just to note that this is also noticeable in the calendar app. Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App->EDS->Indicator-datetime. Wn 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements Just to note that this is also noticeable in the calendar app.
2015-07-16 21:21:32 Bartosz Kosiorek summary Migrate from EDS to dbus Migrate from EDS to dbus to improve performance
2015-07-16 21:21:35 Bartosz Kosiorek ubuntu-clock-app: importance High Low
2015-07-16 21:21:42 Bartosz Kosiorek ubuntu-clock-app: status Confirmed Triaged
2015-07-16 21:22:44 Bartosz Kosiorek description Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App->EDS->Indicator-datetime. Wn 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements Just to note that this is also noticeable in the calendar app. Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App->EDS->Indicator-datetime. Wn 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and-roadmap-ui-toolkit/ Just to note that this is also noticeable in the calendar app.
2015-07-16 21:23:40 Nekhelesh Ramananthan summary Migrate from EDS to dbus to improve performance Migrate from EDS to Dbus to improve performance
2015-07-16 21:23:49 Bartosz Kosiorek description Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App->EDS->Indicator-datetime. Wn 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and-roadmap-ui-toolkit/ Just to note that this is also noticeable in the calendar app. Evolution Data Server should be replaced with dbus. Right now it is man in the middle which hits performance, Clock App->EDS->Indicator-datetime. In 16.04, we are removing the middle man EDS from the equation so alarms created will appear instantly in the indicator and other improvements https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and-roadmap-ui-toolkit/ Just to note that this is also noticeable in the calendar app.