touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #90444
[Bug 1362548] Re: Alarms take several seconds to save (~5seconds) which is quite long compared to existing solutions
** Description changed:
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.
** Description changed:
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.
** Summary changed:
- Alarms take several seconds to save (~5seconds) which is quite long compared to existing solutions
+ Migrate from EDS to dbus
** Description changed:
- 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.
+ 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.
** Summary changed:
- Migrate from EDS to dbus
+ Migrate from EDS to dbus to improve performance
** Changed in: ubuntu-clock-app
Importance: High => Low
** Changed in: ubuntu-clock-app
Status: Confirmed => Triaged
** Description changed:
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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtorganizer5-eds in
Ubuntu.
https://bugs.launchpad.net/bugs/1362548
Title:
Migrate from EDS to Dbus to improve performance
Status in Ubuntu Clock App:
Triaged
Status in qtorganizer5-eds package in Ubuntu:
Confirmed
Bug 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.
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362548/+subscriptions
References