Chris Vervais wrote:
Is there a doc out there somewhere that talks about the scalability of
the IMAP IDLE implementation? I've never dealt with enpd so I don't know
how well it scales.
So far I'm leaning towards running one enpd on every mailstore we have
rather than running one that is responsible for all mailstores.
Currently the entire deployment sees up to 600,000+ simultaneous
connections at a time. Which is spread over several stores that handle
12,000+ of those connections each.
But, if I do expose IMAP idle I expect that number will go up some as
clients that make use of idle will well, idle rather than disconnecting
and then reconnecting later.
Or, it could stay the same as the clients would have a persistent
connection open anyways that sits there and does status commands every
now and then.
haven't seen an answer to this, so I'll take a shot...
If you are using ENS because you have some program which you want to receive
notifications of various events, then it would be more convenient for all the
store systems to publish those events to one enpd and your program to subscribe
to that one enpd.
But if you are using ENS only for IMAP IDLE, there is not much use to having all
that event traffic to a central enpd and back to imapd on the individual store.
You might as well use one enpd per store.
Kelly
