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 442186 - The first time I delete a message in my Exchange account it takes ~30 s.
The first time I delete a message in my Exchange account it takes ~30 s.
Status: RESOLVED OBSOLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.10.x
Other All
: Normal major
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2007-05-29 23:42 UTC by Paul Smith
Modified: 2010-01-15 19:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Paul Smith 2007-05-29 23:42:24 UTC
Please describe the problem:
The first time I delete a message in my Exchange account after starting Evolution, it takes about 30 seconds or so to complete.  During that time, Evolution is completely frozen.

Once that's done, subsequent deletes go quite quickly.  But if I exit and restart Evo, the first delete again takes ~30s.  Note this is a normal "Quit", I don't need to --force-shutdown to see the delay behavior.

Steps to reproduce:
1. Start Evolution
2. Connect to an Exchange account
3. Delete a message, either with the Delete button or C-d (doesn't matter).


Actual results:
The delete operation takes about 30 seconds to complete during which Evo is frozen and nothing can be done.

Expected results:
The delete to complete quickly, as it does for the second and subsequent deletes.

Does this happen every time?
Yes.

Other information:
I'm using Ubuntu 7.04, but this problem happened with older versions of Evolution as well, including Evo 2.8/Gnome 2.16 in Ubuntu 6.10 and Evo 2.6/Gnome 2.14 in Evo 6.06.
Comment 1 Paul Smith 2007-07-30 16:03:43 UTC
I have been trying 2.11.4 and 2.11.5 and this problem is lessened: now it takes a very long time (even a bit longer, I think) to perform the first delete after you create a new account, but it is not very much slower to delete after that, even right after you've restarted Evo.
Comment 2 Veerapuram Varadhan 2007-08-07 10:40:52 UTC
First delete after creation of account would just take the same amount it took in 2.11.4 (may be a couple of seconds more and not more than that).  First Delete initiates a folder-scan of Deleted Items and if no summary is created for that folder, the folder-scan would take more time and that is what is happening with the first-delete after creation of account.

I will be working on further optimizing this after I fix the missing mails issue.

Paul:  Can you post the difference w.r.t timings in First delete after restart?  That would give everyone the idea about the optimization in 2.11.5 and also the hackers to see a possibility for saving some more seconds.
Comment 3 Paul Smith 2007-08-07 17:08:55 UTC
When I say "longer" I mean longer than a delete after restarting Evo in 2.10 and below.

Anyway, here are some timings for Evo 2.11.6.1, build from SVN HEAD as of this morning.  Note this was built for debugging so it has full E2K_DEBUG and CAMEL_DEBUG set, and it's compiled with no optimization enabled (just -g).  I'm running on a Dell Dimension 9150 (dual core Intel 3GHz) with 1G RAM, and my server is running Exchange 2003.  I don't have timings for older (pre-2.11) Evo but readers can obtain those themselves.  My Inbox on the Exchange server has about 160 messages (all read) and my Deleted Items folder has about 1480 messages.

First delete after creating an account:   50s
Subsequent deletes: <1s
Subsequent deletes after restarting Evo: <1s

It's a bit odd because my system doesn't seem to be doing much (according to my CPU monitor) during those 50s.

What I'm saying is that the 50 seconds above seems longer to me than the previous wait when you deleted after restarting Evo 2.10.  However, this is still a huge improvement since it only happens once upon creating the account rather than every restart.

I have occasionally seen longer times, but I've occasionally seen longer times for every operation so I don't think it's operation specific.  It's either an Evo glitch or a glitch in the Exchange server or network connection.  In any case, it's definitely a different bug than this.
Comment 4 Paul Smith 2010-01-15 19:28:20 UTC
I don't see this anymore so I'm closing this.