OK, I'll try to figure out how to get at tcpdump -- it's not as simple as typing tcpdump > tmp.file, is it?
I don't think I'm using any vfolders at all but maybe something got turned on when I upgraded to 1.20. I'll have to check this tomorrow morning, when I'm back at the computer that has 1.20. Scott On Wed, 2002-11-20 at 15:54, Jeffrey Stedfast wrote: > Mioght be good to get a tcpdump of each of evolution 1.0.8 and 1.2.0 - > it might provide clues as to what it is actually fetching - because > afaik, it shouldn't be fetching headers *again*. > > Do you have body searches in your vfolders or something maybe? > > Jeff > > On Wed, 2002-11-20 at 18:03, Scott Otterson wrote: > > What a relief! Alright, I'll submit a bug on the hanging problem. > > > > As for IMAP speed, I'm still not sure how to test 1.08 v.s. 1.20 on the > > amount/number of times it spends downloading headers. I've got Redhat > > 8.0 installed with RPM's halfways to Ximian Gnome and, although I don't > > have much experience with this, I have enough to know that rebuilding > > 1.08 on this system will be Hell. > > > > So, the best way to go back to 1.08 is to pry the disk out of the center > > of my laptop and reinstall the old one containing 1.08. I've got a > > thesis to finish, etc., so I really don't want to do this twice. I want > > to figure out a good way to do the test before I start. > > > > Scott > > > > On Wed, 2002-11-20 at 14:10, Not Zed wrote: > > > On Thu, 2002-11-21 at 04:15, Scott Otterson wrote: > > > > Jeff, those are great numbers but I suspect the test isn't measuring the > > > > thing I'm talking about. What I'm talking about is amount of time > > > > evolution spends rechecking message headers and updating vfolders. For > > > > example, I just did this: > > > > > > > > - started evolution > > > > - waited for the INBOX to show up (lots of messages about vfolders > > > > scanning for new headers) > > > > - open an email > > > > - delete that email > > > > - click on a different email header > > > > - again, I see a bunch of messages about scanning for new headers, etc. > > > > > > > > The delay for the 2nd check is about as long as when I first started > > > > evolution. I haven't yet figured out when evolution decides to go > > > > through all this checking and rechecking but it seems to be quite a lot > > > > more often than 1.08. This really makes evolution harder to use on a > > > > slow modem connection. > > > > > > > > Can you think of a way to test this aspect? Do you think that the > > > > checking and rechecking is because of evolutions's interaction with UW > > > > IMAP v.s. other kinds of IMAP? If so, the problem is solvable because > > > > the mozilla IMAP doesn't spend this much time checking and rechecking. > > > > > > This could be anything, it definetly isn't the tcp code. Its probably a > > > vfolder or imap thread deadlock or something like that. > > > > > > Not much use discussing it here, you need to create a bug, and attach a > > > backtrace of all threads of evolution-mail when it is in a solidly hung > > > state. > > > > > > > > > > > > > > > > > _______________________________________________ > > evolution maillist - [EMAIL PROTECTED] > > http://lists.ximian.com/mailman/listinfo/evolution > -- > Jeffrey Stedfast > Evolution Hacker - Ximian, Inc. > [EMAIL PROTECTED] - www.ximian.com > _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
