Fast imap server for larger foldersFast search for IMAP?migrating email public folders from cyrus imap to exchange 2010Migrating Outlook PSTs -> Maildir via IMAPFast way of copying IMAP to IMAP on CentOSDefault permissions for courier imap foldersMaintain email timestamp when transferring between email servers using an email clientIMAP server can't read (open) mails using fetchmail, procmail & dovecotEscaping Double Quotes in IMAP Search StringThunderbird sub folders grayed out after migrating to new mail server (postfix,dovecot,docker)Dovecot imap send spam to junk

Generate basis elements of the Steenrod algebra

Which languages would be most useful in Europe at the end of the 19th century?

Non-aqueous eyes?

Is it possible for a vehicle to be manufactured without a catalytic converter?

Who enforces MPAA rating adherence?

Does the 2019 UA Artificer's Many-Handed Pouch infusion enable unlimited infinite-range cross-planar communication?

Entire circuit dead after GFCI outlet

Wooden cooking layout

Can a catering trolley removal result in a measurable reduction in emissions?

Overlapping String-Blocks

How to trick the reader into thinking they're following a redshirt instead of the protagonist?

Cascading Switches. Will it affect performance?

Live action TV show where High school Kids go into the virtual world and have to clear levels

Second (easy access) account in case my bank screws up

60s or 70s novel about Empire of Man making 1st contact with 1st discovered alien race

Single-key teletype?

How did old MS-DOS games utilize various graphic cards?

How to communicate to my GM that not being allowed to use stealth isn't fun for me?

How does the Around command at zero work?

Is an entry level DSLR going to shoot nice portrait pictures?

How to handle (one's own) self-harm scars (on the arm), in a work environment?

Traversing Oceania: A Cryptic Journey

What aircraft was used as Air Force One for the flight between Southampton and Shannon?

What is the color of artificial intelligence?



Fast imap server for larger folders


Fast search for IMAP?migrating email public folders from cyrus imap to exchange 2010Migrating Outlook PSTs -> Maildir via IMAPFast way of copying IMAP to IMAP on CentOSDefault permissions for courier imap foldersMaintain email timestamp when transferring between email servers using an email clientIMAP server can't read (open) mails using fetchmail, procmail & dovecotEscaping Double Quotes in IMAP Search StringThunderbird sub folders grayed out after migrating to new mail server (postfix,dovecot,docker)Dovecot imap send spam to junk






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








6















I'm looking for an imap server that is fast with larger folders. Say 20'000-100'000 emails per folder.



Currently I'm using dovecot, and opening a folder can take 10 seconds, and the HD light on the imap server is brinking like crazy.



I'm using alpine as a client, and it only lists the newest mails by default, so it's not that my client is trying to transfer everything when opening the mailbox. This can be seen in that when I scroll it has to load the subject lines for the next page (the first time I scroll there).



I'm using maildir on XFS.



Edit: I ask since it's not much data, in the grand scheme of things. If this was in a SQL database then getting the subject lines of the newest 40 messages would not take 10 seconds for a folder of 40'000 emails. The only data needed is:



SELECT date, from, subject FROM emails ORDER BY date DESC LIMIT 40;


Any ideas?










share|improve this question
























  • I would suggest splitting these folders up. It will be nicer for the user and for the server.

    – alex
    Nov 26 '09 at 22:53











  • I'm the user, and no it wouldn't be. It's the ugly fix I'm going with though.

    – Thomas
    Nov 27 '09 at 17:35

















6















I'm looking for an imap server that is fast with larger folders. Say 20'000-100'000 emails per folder.



Currently I'm using dovecot, and opening a folder can take 10 seconds, and the HD light on the imap server is brinking like crazy.



I'm using alpine as a client, and it only lists the newest mails by default, so it's not that my client is trying to transfer everything when opening the mailbox. This can be seen in that when I scroll it has to load the subject lines for the next page (the first time I scroll there).



I'm using maildir on XFS.



Edit: I ask since it's not much data, in the grand scheme of things. If this was in a SQL database then getting the subject lines of the newest 40 messages would not take 10 seconds for a folder of 40'000 emails. The only data needed is:



SELECT date, from, subject FROM emails ORDER BY date DESC LIMIT 40;


Any ideas?










share|improve this question
























  • I would suggest splitting these folders up. It will be nicer for the user and for the server.

    – alex
    Nov 26 '09 at 22:53











  • I'm the user, and no it wouldn't be. It's the ugly fix I'm going with though.

    – Thomas
    Nov 27 '09 at 17:35













6












6








6


5






I'm looking for an imap server that is fast with larger folders. Say 20'000-100'000 emails per folder.



Currently I'm using dovecot, and opening a folder can take 10 seconds, and the HD light on the imap server is brinking like crazy.



I'm using alpine as a client, and it only lists the newest mails by default, so it's not that my client is trying to transfer everything when opening the mailbox. This can be seen in that when I scroll it has to load the subject lines for the next page (the first time I scroll there).



I'm using maildir on XFS.



Edit: I ask since it's not much data, in the grand scheme of things. If this was in a SQL database then getting the subject lines of the newest 40 messages would not take 10 seconds for a folder of 40'000 emails. The only data needed is:



SELECT date, from, subject FROM emails ORDER BY date DESC LIMIT 40;


Any ideas?










share|improve this question
















I'm looking for an imap server that is fast with larger folders. Say 20'000-100'000 emails per folder.



Currently I'm using dovecot, and opening a folder can take 10 seconds, and the HD light on the imap server is brinking like crazy.



I'm using alpine as a client, and it only lists the newest mails by default, so it's not that my client is trying to transfer everything when opening the mailbox. This can be seen in that when I scroll it has to load the subject lines for the next page (the first time I scroll there).



I'm using maildir on XFS.



Edit: I ask since it's not much data, in the grand scheme of things. If this was in a SQL database then getting the subject lines of the newest 40 messages would not take 10 seconds for a folder of 40'000 emails. The only data needed is:



SELECT date, from, subject FROM emails ORDER BY date DESC LIMIT 40;


Any ideas?







linux imap






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 24 '09 at 12:28







Thomas

















asked Aug 24 '09 at 8:53









ThomasThomas

1,3361014




1,3361014












  • I would suggest splitting these folders up. It will be nicer for the user and for the server.

    – alex
    Nov 26 '09 at 22:53











  • I'm the user, and no it wouldn't be. It's the ugly fix I'm going with though.

    – Thomas
    Nov 27 '09 at 17:35

















  • I would suggest splitting these folders up. It will be nicer for the user and for the server.

    – alex
    Nov 26 '09 at 22:53











  • I'm the user, and no it wouldn't be. It's the ugly fix I'm going with though.

    – Thomas
    Nov 27 '09 at 17:35
















I would suggest splitting these folders up. It will be nicer for the user and for the server.

– alex
Nov 26 '09 at 22:53





I would suggest splitting these folders up. It will be nicer for the user and for the server.

– alex
Nov 26 '09 at 22:53













I'm the user, and no it wouldn't be. It's the ugly fix I'm going with though.

– Thomas
Nov 27 '09 at 17:35





I'm the user, and no it wouldn't be. It's the ugly fix I'm going with though.

– Thomas
Nov 27 '09 at 17:35










4 Answers
4






active

oldest

votes


















4














Dovecot is actually pretty good, performance-wise. Dovecot's Performance Tuning wiki page has a few tips and tricks to further improve performance. Keeping indices and maildirs on separate disks is a good thing to start with, if at all possible for you. You could also evaluate switching to Dovecot's dbox storage format.






share|improve this answer

























  • I've tried to optimize using the tuning page. This is as good as I got it. I'll try dbox.

    – Thomas
    Aug 24 '09 at 12:31











  • dovecot is bonkers fast

    – hendry
    Feb 2 '12 at 16:18


















3














Maybe you could try using a database engine for message storage, instead of using Maildir/Maildir++ mailboxes. This can be done with dbmail.



I don't know how reliable dbmail is for a production environment, but since you already have virtualization working, you could set it up on another VM for testing purposes and see how it performs on your environment.



Here's an overview of dbmail's architecture:



alt text
(source: dbmail.org)






share|improve this answer

























  • I don't think that the graphic adds any value to the otherwise nice answer. There's also an interesting thread on the dovecot mailing list, benchmarking some aspects of dovecot vs dbmail (dovecot.org/list/dovecot/2007-May/022599.html).

    – earl
    Aug 24 '09 at 17:42











  • Earl, thanks for the feedback. I think that the OP mileage might vary, and that's why it would be useful for him to perform some tests on his own environment. It's not my intention to question the value of the benchmarks that you linked, but since those tests were run 2.5 years (and 6 releases) ago, it wouldn't be a bad idea to check again.

    – mfriedman
    Aug 24 '09 at 18:29











  • Oh, and regarding the diagram that I've added to my answer, I respectfully disagree. It shows how the pieces fit together, what are the DBMail and the Non-DBMail components, and how they interact with each other. Even when I agree that the picture may be beyond what was asked, I think that it helps to illustrate how this particular solution works. And, as the saying goes, "a picture is worth a thousand words". Best regards, Marcus.

    – mfriedman
    Aug 24 '09 at 18:35











  • Thank you for the link and diagram. I have done some subjective "feel" benchmarking and it seems that dovecot is slightly faster once it has cached the index, but since emails keep trickling in the cache is soon invalidated so in practice I get the slow hit every time I open the mailbox. dbmail seems to take the hit incrementally on email insertion (makes sense), so it's while it may not be quite as fast, I never get the 10s wait to open a folder. Tested with 44'000 emails in a box.

    – Thomas
    Aug 24 '09 at 21:25


















2














You don't mention the server specs...how much memory are you using, processor, network card/switches are gigabit? And if you look at the server, can you tell what's being maxed out? If it's drive throughput you aren't going to get very far changing the server software



I've been cloning systems over a network and was puzzled to have two systems on a gigabit switch pulling only about 15 MB/sec when I knew that my system was capable of bursts in the 50 MB/s range. Turned out it was the disks bottlenecking on the end-systems (I put a drive into a second IDE channel and did a direct DD, got the same transfer speeds).



You might want to check out the processor/disk/network usage as well as the switch and see if any of those are causing issues. If not those, you could look for ways to boost throughput using separate disks, separating mailboxes to different spindles, check and see if you can get any better throughput using hardware RAID mirroring (I'm not sure how much of a boost in read times off the disks you can get), or possibly moving to higher-performing hard disks with lower latency and bigger caches.






share|improve this answer























  • My point is that it's not much data. 40'000 entries is nothing to a database. It shouldn't be much for an imap server. It's a virtual machine (KVM on Linux) on a quad-core 2.4GHz with raid5 and 8GB RAM, but I've seen this on a physical machine as well. I've benchmarked the disks and network and I get about than 100MByte/sec. But remember that all this is just reading select mail headers (from, flags, subject) of about 40 (the latest) of 40'000 emails. Not even the 40 mail bodies.

    – Thomas
    Aug 24 '09 at 12:22











  • And not 40'000 mail headers. They are loaded on demand if I scroll.

    – Thomas
    Aug 24 '09 at 12:23











  • You probably already checked this (nice specs on the server...shouldn't be that is the issue, I'd think) but is it possibly the client system reading the locally cached information and going back and forth that is causing some slowdown?

    – Bart Silverstrim
    Aug 24 '09 at 12:35


















1














Since you're using dovecot I presume you're already using it's indexing features? I'm not aware of anything (at least, not anything free), that's faster than dovecot.






share|improve this answer























  • Yes, I'm using the indexing. The thing that confuses me is that an SQL database would not take 10 seconds to list the newest 40 rows (when properly indexed). I've updated the question with this.

    – Thomas
    Aug 24 '09 at 12:16









protected by sysadmin1138 Feb 4 '16 at 16:46



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?














4 Answers
4






active

oldest

votes








4 Answers
4






active

oldest

votes









active

oldest

votes






active

oldest

votes









4














Dovecot is actually pretty good, performance-wise. Dovecot's Performance Tuning wiki page has a few tips and tricks to further improve performance. Keeping indices and maildirs on separate disks is a good thing to start with, if at all possible for you. You could also evaluate switching to Dovecot's dbox storage format.






share|improve this answer

























  • I've tried to optimize using the tuning page. This is as good as I got it. I'll try dbox.

    – Thomas
    Aug 24 '09 at 12:31











  • dovecot is bonkers fast

    – hendry
    Feb 2 '12 at 16:18















4














Dovecot is actually pretty good, performance-wise. Dovecot's Performance Tuning wiki page has a few tips and tricks to further improve performance. Keeping indices and maildirs on separate disks is a good thing to start with, if at all possible for you. You could also evaluate switching to Dovecot's dbox storage format.






share|improve this answer

























  • I've tried to optimize using the tuning page. This is as good as I got it. I'll try dbox.

    – Thomas
    Aug 24 '09 at 12:31











  • dovecot is bonkers fast

    – hendry
    Feb 2 '12 at 16:18













4












4








4







Dovecot is actually pretty good, performance-wise. Dovecot's Performance Tuning wiki page has a few tips and tricks to further improve performance. Keeping indices and maildirs on separate disks is a good thing to start with, if at all possible for you. You could also evaluate switching to Dovecot's dbox storage format.






share|improve this answer















Dovecot is actually pretty good, performance-wise. Dovecot's Performance Tuning wiki page has a few tips and tricks to further improve performance. Keeping indices and maildirs on separate disks is a good thing to start with, if at all possible for you. You could also evaluate switching to Dovecot's dbox storage format.







share|improve this answer














share|improve this answer



share|improve this answer








edited Aug 24 '09 at 9:07

























answered Aug 24 '09 at 9:01









earlearl

2,5611816




2,5611816












  • I've tried to optimize using the tuning page. This is as good as I got it. I'll try dbox.

    – Thomas
    Aug 24 '09 at 12:31











  • dovecot is bonkers fast

    – hendry
    Feb 2 '12 at 16:18

















  • I've tried to optimize using the tuning page. This is as good as I got it. I'll try dbox.

    – Thomas
    Aug 24 '09 at 12:31











  • dovecot is bonkers fast

    – hendry
    Feb 2 '12 at 16:18
















I've tried to optimize using the tuning page. This is as good as I got it. I'll try dbox.

– Thomas
Aug 24 '09 at 12:31





I've tried to optimize using the tuning page. This is as good as I got it. I'll try dbox.

– Thomas
Aug 24 '09 at 12:31













dovecot is bonkers fast

– hendry
Feb 2 '12 at 16:18





dovecot is bonkers fast

– hendry
Feb 2 '12 at 16:18













3














Maybe you could try using a database engine for message storage, instead of using Maildir/Maildir++ mailboxes. This can be done with dbmail.



I don't know how reliable dbmail is for a production environment, but since you already have virtualization working, you could set it up on another VM for testing purposes and see how it performs on your environment.



Here's an overview of dbmail's architecture:



alt text
(source: dbmail.org)






share|improve this answer

























  • I don't think that the graphic adds any value to the otherwise nice answer. There's also an interesting thread on the dovecot mailing list, benchmarking some aspects of dovecot vs dbmail (dovecot.org/list/dovecot/2007-May/022599.html).

    – earl
    Aug 24 '09 at 17:42











  • Earl, thanks for the feedback. I think that the OP mileage might vary, and that's why it would be useful for him to perform some tests on his own environment. It's not my intention to question the value of the benchmarks that you linked, but since those tests were run 2.5 years (and 6 releases) ago, it wouldn't be a bad idea to check again.

    – mfriedman
    Aug 24 '09 at 18:29











  • Oh, and regarding the diagram that I've added to my answer, I respectfully disagree. It shows how the pieces fit together, what are the DBMail and the Non-DBMail components, and how they interact with each other. Even when I agree that the picture may be beyond what was asked, I think that it helps to illustrate how this particular solution works. And, as the saying goes, "a picture is worth a thousand words". Best regards, Marcus.

    – mfriedman
    Aug 24 '09 at 18:35











  • Thank you for the link and diagram. I have done some subjective "feel" benchmarking and it seems that dovecot is slightly faster once it has cached the index, but since emails keep trickling in the cache is soon invalidated so in practice I get the slow hit every time I open the mailbox. dbmail seems to take the hit incrementally on email insertion (makes sense), so it's while it may not be quite as fast, I never get the 10s wait to open a folder. Tested with 44'000 emails in a box.

    – Thomas
    Aug 24 '09 at 21:25















3














Maybe you could try using a database engine for message storage, instead of using Maildir/Maildir++ mailboxes. This can be done with dbmail.



I don't know how reliable dbmail is for a production environment, but since you already have virtualization working, you could set it up on another VM for testing purposes and see how it performs on your environment.



Here's an overview of dbmail's architecture:



alt text
(source: dbmail.org)






share|improve this answer

























  • I don't think that the graphic adds any value to the otherwise nice answer. There's also an interesting thread on the dovecot mailing list, benchmarking some aspects of dovecot vs dbmail (dovecot.org/list/dovecot/2007-May/022599.html).

    – earl
    Aug 24 '09 at 17:42











  • Earl, thanks for the feedback. I think that the OP mileage might vary, and that's why it would be useful for him to perform some tests on his own environment. It's not my intention to question the value of the benchmarks that you linked, but since those tests were run 2.5 years (and 6 releases) ago, it wouldn't be a bad idea to check again.

    – mfriedman
    Aug 24 '09 at 18:29











  • Oh, and regarding the diagram that I've added to my answer, I respectfully disagree. It shows how the pieces fit together, what are the DBMail and the Non-DBMail components, and how they interact with each other. Even when I agree that the picture may be beyond what was asked, I think that it helps to illustrate how this particular solution works. And, as the saying goes, "a picture is worth a thousand words". Best regards, Marcus.

    – mfriedman
    Aug 24 '09 at 18:35











  • Thank you for the link and diagram. I have done some subjective "feel" benchmarking and it seems that dovecot is slightly faster once it has cached the index, but since emails keep trickling in the cache is soon invalidated so in practice I get the slow hit every time I open the mailbox. dbmail seems to take the hit incrementally on email insertion (makes sense), so it's while it may not be quite as fast, I never get the 10s wait to open a folder. Tested with 44'000 emails in a box.

    – Thomas
    Aug 24 '09 at 21:25













3












3








3







Maybe you could try using a database engine for message storage, instead of using Maildir/Maildir++ mailboxes. This can be done with dbmail.



I don't know how reliable dbmail is for a production environment, but since you already have virtualization working, you could set it up on another VM for testing purposes and see how it performs on your environment.



Here's an overview of dbmail's architecture:



alt text
(source: dbmail.org)






share|improve this answer















Maybe you could try using a database engine for message storage, instead of using Maildir/Maildir++ mailboxes. This can be done with dbmail.



I don't know how reliable dbmail is for a production environment, but since you already have virtualization working, you could set it up on another VM for testing purposes and see how it performs on your environment.



Here's an overview of dbmail's architecture:



alt text
(source: dbmail.org)







share|improve this answer














share|improve this answer



share|improve this answer








edited May 23 at 23:12









Glorfindel

4921716




4921716










answered Aug 24 '09 at 12:49









mfriedmanmfriedman

1,60411114




1,60411114












  • I don't think that the graphic adds any value to the otherwise nice answer. There's also an interesting thread on the dovecot mailing list, benchmarking some aspects of dovecot vs dbmail (dovecot.org/list/dovecot/2007-May/022599.html).

    – earl
    Aug 24 '09 at 17:42











  • Earl, thanks for the feedback. I think that the OP mileage might vary, and that's why it would be useful for him to perform some tests on his own environment. It's not my intention to question the value of the benchmarks that you linked, but since those tests were run 2.5 years (and 6 releases) ago, it wouldn't be a bad idea to check again.

    – mfriedman
    Aug 24 '09 at 18:29











  • Oh, and regarding the diagram that I've added to my answer, I respectfully disagree. It shows how the pieces fit together, what are the DBMail and the Non-DBMail components, and how they interact with each other. Even when I agree that the picture may be beyond what was asked, I think that it helps to illustrate how this particular solution works. And, as the saying goes, "a picture is worth a thousand words". Best regards, Marcus.

    – mfriedman
    Aug 24 '09 at 18:35











  • Thank you for the link and diagram. I have done some subjective "feel" benchmarking and it seems that dovecot is slightly faster once it has cached the index, but since emails keep trickling in the cache is soon invalidated so in practice I get the slow hit every time I open the mailbox. dbmail seems to take the hit incrementally on email insertion (makes sense), so it's while it may not be quite as fast, I never get the 10s wait to open a folder. Tested with 44'000 emails in a box.

    – Thomas
    Aug 24 '09 at 21:25

















  • I don't think that the graphic adds any value to the otherwise nice answer. There's also an interesting thread on the dovecot mailing list, benchmarking some aspects of dovecot vs dbmail (dovecot.org/list/dovecot/2007-May/022599.html).

    – earl
    Aug 24 '09 at 17:42











  • Earl, thanks for the feedback. I think that the OP mileage might vary, and that's why it would be useful for him to perform some tests on his own environment. It's not my intention to question the value of the benchmarks that you linked, but since those tests were run 2.5 years (and 6 releases) ago, it wouldn't be a bad idea to check again.

    – mfriedman
    Aug 24 '09 at 18:29











  • Oh, and regarding the diagram that I've added to my answer, I respectfully disagree. It shows how the pieces fit together, what are the DBMail and the Non-DBMail components, and how they interact with each other. Even when I agree that the picture may be beyond what was asked, I think that it helps to illustrate how this particular solution works. And, as the saying goes, "a picture is worth a thousand words". Best regards, Marcus.

    – mfriedman
    Aug 24 '09 at 18:35











  • Thank you for the link and diagram. I have done some subjective "feel" benchmarking and it seems that dovecot is slightly faster once it has cached the index, but since emails keep trickling in the cache is soon invalidated so in practice I get the slow hit every time I open the mailbox. dbmail seems to take the hit incrementally on email insertion (makes sense), so it's while it may not be quite as fast, I never get the 10s wait to open a folder. Tested with 44'000 emails in a box.

    – Thomas
    Aug 24 '09 at 21:25
















I don't think that the graphic adds any value to the otherwise nice answer. There's also an interesting thread on the dovecot mailing list, benchmarking some aspects of dovecot vs dbmail (dovecot.org/list/dovecot/2007-May/022599.html).

– earl
Aug 24 '09 at 17:42





I don't think that the graphic adds any value to the otherwise nice answer. There's also an interesting thread on the dovecot mailing list, benchmarking some aspects of dovecot vs dbmail (dovecot.org/list/dovecot/2007-May/022599.html).

– earl
Aug 24 '09 at 17:42













Earl, thanks for the feedback. I think that the OP mileage might vary, and that's why it would be useful for him to perform some tests on his own environment. It's not my intention to question the value of the benchmarks that you linked, but since those tests were run 2.5 years (and 6 releases) ago, it wouldn't be a bad idea to check again.

– mfriedman
Aug 24 '09 at 18:29





Earl, thanks for the feedback. I think that the OP mileage might vary, and that's why it would be useful for him to perform some tests on his own environment. It's not my intention to question the value of the benchmarks that you linked, but since those tests were run 2.5 years (and 6 releases) ago, it wouldn't be a bad idea to check again.

– mfriedman
Aug 24 '09 at 18:29













Oh, and regarding the diagram that I've added to my answer, I respectfully disagree. It shows how the pieces fit together, what are the DBMail and the Non-DBMail components, and how they interact with each other. Even when I agree that the picture may be beyond what was asked, I think that it helps to illustrate how this particular solution works. And, as the saying goes, "a picture is worth a thousand words". Best regards, Marcus.

– mfriedman
Aug 24 '09 at 18:35





Oh, and regarding the diagram that I've added to my answer, I respectfully disagree. It shows how the pieces fit together, what are the DBMail and the Non-DBMail components, and how they interact with each other. Even when I agree that the picture may be beyond what was asked, I think that it helps to illustrate how this particular solution works. And, as the saying goes, "a picture is worth a thousand words". Best regards, Marcus.

– mfriedman
Aug 24 '09 at 18:35













Thank you for the link and diagram. I have done some subjective "feel" benchmarking and it seems that dovecot is slightly faster once it has cached the index, but since emails keep trickling in the cache is soon invalidated so in practice I get the slow hit every time I open the mailbox. dbmail seems to take the hit incrementally on email insertion (makes sense), so it's while it may not be quite as fast, I never get the 10s wait to open a folder. Tested with 44'000 emails in a box.

– Thomas
Aug 24 '09 at 21:25





Thank you for the link and diagram. I have done some subjective "feel" benchmarking and it seems that dovecot is slightly faster once it has cached the index, but since emails keep trickling in the cache is soon invalidated so in practice I get the slow hit every time I open the mailbox. dbmail seems to take the hit incrementally on email insertion (makes sense), so it's while it may not be quite as fast, I never get the 10s wait to open a folder. Tested with 44'000 emails in a box.

– Thomas
Aug 24 '09 at 21:25











2














You don't mention the server specs...how much memory are you using, processor, network card/switches are gigabit? And if you look at the server, can you tell what's being maxed out? If it's drive throughput you aren't going to get very far changing the server software



I've been cloning systems over a network and was puzzled to have two systems on a gigabit switch pulling only about 15 MB/sec when I knew that my system was capable of bursts in the 50 MB/s range. Turned out it was the disks bottlenecking on the end-systems (I put a drive into a second IDE channel and did a direct DD, got the same transfer speeds).



You might want to check out the processor/disk/network usage as well as the switch and see if any of those are causing issues. If not those, you could look for ways to boost throughput using separate disks, separating mailboxes to different spindles, check and see if you can get any better throughput using hardware RAID mirroring (I'm not sure how much of a boost in read times off the disks you can get), or possibly moving to higher-performing hard disks with lower latency and bigger caches.






share|improve this answer























  • My point is that it's not much data. 40'000 entries is nothing to a database. It shouldn't be much for an imap server. It's a virtual machine (KVM on Linux) on a quad-core 2.4GHz with raid5 and 8GB RAM, but I've seen this on a physical machine as well. I've benchmarked the disks and network and I get about than 100MByte/sec. But remember that all this is just reading select mail headers (from, flags, subject) of about 40 (the latest) of 40'000 emails. Not even the 40 mail bodies.

    – Thomas
    Aug 24 '09 at 12:22











  • And not 40'000 mail headers. They are loaded on demand if I scroll.

    – Thomas
    Aug 24 '09 at 12:23











  • You probably already checked this (nice specs on the server...shouldn't be that is the issue, I'd think) but is it possibly the client system reading the locally cached information and going back and forth that is causing some slowdown?

    – Bart Silverstrim
    Aug 24 '09 at 12:35















2














You don't mention the server specs...how much memory are you using, processor, network card/switches are gigabit? And if you look at the server, can you tell what's being maxed out? If it's drive throughput you aren't going to get very far changing the server software



I've been cloning systems over a network and was puzzled to have two systems on a gigabit switch pulling only about 15 MB/sec when I knew that my system was capable of bursts in the 50 MB/s range. Turned out it was the disks bottlenecking on the end-systems (I put a drive into a second IDE channel and did a direct DD, got the same transfer speeds).



You might want to check out the processor/disk/network usage as well as the switch and see if any of those are causing issues. If not those, you could look for ways to boost throughput using separate disks, separating mailboxes to different spindles, check and see if you can get any better throughput using hardware RAID mirroring (I'm not sure how much of a boost in read times off the disks you can get), or possibly moving to higher-performing hard disks with lower latency and bigger caches.






share|improve this answer























  • My point is that it's not much data. 40'000 entries is nothing to a database. It shouldn't be much for an imap server. It's a virtual machine (KVM on Linux) on a quad-core 2.4GHz with raid5 and 8GB RAM, but I've seen this on a physical machine as well. I've benchmarked the disks and network and I get about than 100MByte/sec. But remember that all this is just reading select mail headers (from, flags, subject) of about 40 (the latest) of 40'000 emails. Not even the 40 mail bodies.

    – Thomas
    Aug 24 '09 at 12:22











  • And not 40'000 mail headers. They are loaded on demand if I scroll.

    – Thomas
    Aug 24 '09 at 12:23











  • You probably already checked this (nice specs on the server...shouldn't be that is the issue, I'd think) but is it possibly the client system reading the locally cached information and going back and forth that is causing some slowdown?

    – Bart Silverstrim
    Aug 24 '09 at 12:35













2












2








2







You don't mention the server specs...how much memory are you using, processor, network card/switches are gigabit? And if you look at the server, can you tell what's being maxed out? If it's drive throughput you aren't going to get very far changing the server software



I've been cloning systems over a network and was puzzled to have two systems on a gigabit switch pulling only about 15 MB/sec when I knew that my system was capable of bursts in the 50 MB/s range. Turned out it was the disks bottlenecking on the end-systems (I put a drive into a second IDE channel and did a direct DD, got the same transfer speeds).



You might want to check out the processor/disk/network usage as well as the switch and see if any of those are causing issues. If not those, you could look for ways to boost throughput using separate disks, separating mailboxes to different spindles, check and see if you can get any better throughput using hardware RAID mirroring (I'm not sure how much of a boost in read times off the disks you can get), or possibly moving to higher-performing hard disks with lower latency and bigger caches.






share|improve this answer













You don't mention the server specs...how much memory are you using, processor, network card/switches are gigabit? And if you look at the server, can you tell what's being maxed out? If it's drive throughput you aren't going to get very far changing the server software



I've been cloning systems over a network and was puzzled to have two systems on a gigabit switch pulling only about 15 MB/sec when I knew that my system was capable of bursts in the 50 MB/s range. Turned out it was the disks bottlenecking on the end-systems (I put a drive into a second IDE channel and did a direct DD, got the same transfer speeds).



You might want to check out the processor/disk/network usage as well as the switch and see if any of those are causing issues. If not those, you could look for ways to boost throughput using separate disks, separating mailboxes to different spindles, check and see if you can get any better throughput using hardware RAID mirroring (I'm not sure how much of a boost in read times off the disks you can get), or possibly moving to higher-performing hard disks with lower latency and bigger caches.







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 24 '09 at 12:07









Bart SilverstrimBart Silverstrim

29.5k95684




29.5k95684












  • My point is that it's not much data. 40'000 entries is nothing to a database. It shouldn't be much for an imap server. It's a virtual machine (KVM on Linux) on a quad-core 2.4GHz with raid5 and 8GB RAM, but I've seen this on a physical machine as well. I've benchmarked the disks and network and I get about than 100MByte/sec. But remember that all this is just reading select mail headers (from, flags, subject) of about 40 (the latest) of 40'000 emails. Not even the 40 mail bodies.

    – Thomas
    Aug 24 '09 at 12:22











  • And not 40'000 mail headers. They are loaded on demand if I scroll.

    – Thomas
    Aug 24 '09 at 12:23











  • You probably already checked this (nice specs on the server...shouldn't be that is the issue, I'd think) but is it possibly the client system reading the locally cached information and going back and forth that is causing some slowdown?

    – Bart Silverstrim
    Aug 24 '09 at 12:35

















  • My point is that it's not much data. 40'000 entries is nothing to a database. It shouldn't be much for an imap server. It's a virtual machine (KVM on Linux) on a quad-core 2.4GHz with raid5 and 8GB RAM, but I've seen this on a physical machine as well. I've benchmarked the disks and network and I get about than 100MByte/sec. But remember that all this is just reading select mail headers (from, flags, subject) of about 40 (the latest) of 40'000 emails. Not even the 40 mail bodies.

    – Thomas
    Aug 24 '09 at 12:22











  • And not 40'000 mail headers. They are loaded on demand if I scroll.

    – Thomas
    Aug 24 '09 at 12:23











  • You probably already checked this (nice specs on the server...shouldn't be that is the issue, I'd think) but is it possibly the client system reading the locally cached information and going back and forth that is causing some slowdown?

    – Bart Silverstrim
    Aug 24 '09 at 12:35
















My point is that it's not much data. 40'000 entries is nothing to a database. It shouldn't be much for an imap server. It's a virtual machine (KVM on Linux) on a quad-core 2.4GHz with raid5 and 8GB RAM, but I've seen this on a physical machine as well. I've benchmarked the disks and network and I get about than 100MByte/sec. But remember that all this is just reading select mail headers (from, flags, subject) of about 40 (the latest) of 40'000 emails. Not even the 40 mail bodies.

– Thomas
Aug 24 '09 at 12:22





My point is that it's not much data. 40'000 entries is nothing to a database. It shouldn't be much for an imap server. It's a virtual machine (KVM on Linux) on a quad-core 2.4GHz with raid5 and 8GB RAM, but I've seen this on a physical machine as well. I've benchmarked the disks and network and I get about than 100MByte/sec. But remember that all this is just reading select mail headers (from, flags, subject) of about 40 (the latest) of 40'000 emails. Not even the 40 mail bodies.

– Thomas
Aug 24 '09 at 12:22













And not 40'000 mail headers. They are loaded on demand if I scroll.

– Thomas
Aug 24 '09 at 12:23





And not 40'000 mail headers. They are loaded on demand if I scroll.

– Thomas
Aug 24 '09 at 12:23













You probably already checked this (nice specs on the server...shouldn't be that is the issue, I'd think) but is it possibly the client system reading the locally cached information and going back and forth that is causing some slowdown?

– Bart Silverstrim
Aug 24 '09 at 12:35





You probably already checked this (nice specs on the server...shouldn't be that is the issue, I'd think) but is it possibly the client system reading the locally cached information and going back and forth that is causing some slowdown?

– Bart Silverstrim
Aug 24 '09 at 12:35











1














Since you're using dovecot I presume you're already using it's indexing features? I'm not aware of anything (at least, not anything free), that's faster than dovecot.






share|improve this answer























  • Yes, I'm using the indexing. The thing that confuses me is that an SQL database would not take 10 seconds to list the newest 40 rows (when properly indexed). I've updated the question with this.

    – Thomas
    Aug 24 '09 at 12:16















1














Since you're using dovecot I presume you're already using it's indexing features? I'm not aware of anything (at least, not anything free), that's faster than dovecot.






share|improve this answer























  • Yes, I'm using the indexing. The thing that confuses me is that an SQL database would not take 10 seconds to list the newest 40 rows (when properly indexed). I've updated the question with this.

    – Thomas
    Aug 24 '09 at 12:16













1












1








1







Since you're using dovecot I presume you're already using it's indexing features? I'm not aware of anything (at least, not anything free), that's faster than dovecot.






share|improve this answer













Since you're using dovecot I presume you're already using it's indexing features? I'm not aware of anything (at least, not anything free), that's faster than dovecot.







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 24 '09 at 8:56









theotherreceivetheotherreceive

7,61712543




7,61712543












  • Yes, I'm using the indexing. The thing that confuses me is that an SQL database would not take 10 seconds to list the newest 40 rows (when properly indexed). I've updated the question with this.

    – Thomas
    Aug 24 '09 at 12:16

















  • Yes, I'm using the indexing. The thing that confuses me is that an SQL database would not take 10 seconds to list the newest 40 rows (when properly indexed). I've updated the question with this.

    – Thomas
    Aug 24 '09 at 12:16
















Yes, I'm using the indexing. The thing that confuses me is that an SQL database would not take 10 seconds to list the newest 40 rows (when properly indexed). I've updated the question with this.

– Thomas
Aug 24 '09 at 12:16





Yes, I'm using the indexing. The thing that confuses me is that an SQL database would not take 10 seconds to list the newest 40 rows (when properly indexed). I've updated the question with this.

– Thomas
Aug 24 '09 at 12:16





protected by sysadmin1138 Feb 4 '16 at 16:46



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?



Popular posts from this blog

Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020