Closed pushkarsingh closed 11 years ago
I'm fairly sure we closed this issue a while ago. Have you pulled all the latest changes in?
I think @pushkarsingh is correct. I need to fix it.
It's a MailCore 2 issue. I think the main thread gets blocked for a few seconds while the IMAP calls is in finishing.
@CodaFi I have pulled the latest, the UI stops responding after this happens
BTW, I am not sure what is the fastest way of getting few lines of message body to show for the list of emails.
Could you show other threads?
to get few lines of a message body, htmlRendering() + flattenHTML is the way to go.
Here are rest of threads,
thanks, I was calling htmlRendering, but feel we can improve to have a simple call ti get message body, similar to MailCore1
Could you open an other issue to get few lines of an email? Describe how you did in using mailcore and how you do it using mailcore2. I definitively want to improve it.
Could you try with the latest changes now? Thanks!
Looks good !
I understand we have our own implementation of OperationQueue for portability reason. I was wondering if GCD's dispatch queues or NSOperation Queue, would have given a better performance. RIght now all pthreads are created with default priority.
Thanks
Since network performance is the main performance hit, we don't need to optimize that yet. Since I want to make sure the implementation will work on all platforms, I want to keep the implementation for now. Until we really encounter a real performance issue.
Closing this issue.
Do you have any suggestions how we can improve the network performance? right now the numbers are on higher side, I have a 20mbps/5mbps connection and
fetchMessagesByUIDOperationWithFolder for a block of 50 mails excluding message body takes ~1 sec, and block of 200 mails takes ~4 secs
The server you're talking to probably limits the bandwidth (or has limited performance).
I am using imap.gmail.com
Reverted the fix. It caused a crash when sending emails. See #88.
Do we have a workaround for now? I am really blocked on this one.
I'm going to retry the fix and fix the crash issue introduce when using SMTP. For now, you can cherry pick the change in your working set while waiting for the fix.
The other problem with that fix was that it used to crash every time I enter wrong credentials, I will upload the stack trace , I need to go back to that commit.
Since I could not reproduce the issue with SMTP, I added the fix again.
For the other crash, was it the issue #75?
The main thread get frequently blocked in MCOperationQueue.cc at line #71 mailsem_down(mStopSem)
This is happening when I call following operation multiple time.