After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 704771 - Performance regression when compose window is open - EWS
Performance regression when compose window is open - EWS
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
3.8.x (obsolete)
Other Linux
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer]
Depends on:
Blocks: 703515
 
 
Reported: 2013-07-23 23:37 UTC by PJ Waskiewicz
Modified: 2013-07-26 10:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description PJ Waskiewicz 2013-07-23 23:37:15 UTC
Using evolution-ews, my X session becomes sluggish when switching between windows or switching virtual desktops (Cinnamon) only when a Compose mail window is open.  Nothing needs to be typed into the window, just once it's open things become choppy.

Once the Compose window has been closed, either by closing or sending the email, performance of the X session returns to normal (smooth transitions).

Package versions being used:

evolution-data-server-devel-3.8.3-1.fc19.x86_64
evolution-3.8.3-2.fc19.x86_64
evolution-help-3.8.3-2.fc19.noarch
evolution-data-server-3.8.3-1.fc19.x86_64
evolution-ews-3.8.3-1.fc19.x86_64

Hardware is a Lenovo Thinkpad X220, 8 GB of RAM, Intel SSD.
Comment 1 Milan Crha 2013-07-25 15:56:12 UTC
Thanks for a bug report. Can it be a driver issue? I do not see how an opened inactive composer window of evolution can cause such behaviour. I didn't notice it, at least. I noticed slowness when opening or closing the composer window when there are defined many (50+) mail accounts, together with many calendars/books/..., but nothing when left the composer window as is. Could you try to investigate when exactly this happens, please? I would also try to involve sysprof or similar tool, to try to see where the CPU is busy.
Comment 2 PJ Waskiewicz 2013-07-25 17:39:17 UTC
This may be related to overall memory footprint.  I'm running the 3.8.4 data-server now, which David indicated addressed some of the addressbook-data-factory memory appetite.  I can open my Compose windows without seeing this performance hit anymore.

Feel free to close this, it appears 3.8.4-data-server has fixed this adequately.
Comment 3 Matthew Barnes 2013-07-26 10:32:13 UTC
Closing as INCOMPLETE since the exact cause was never pinned down.