On 01-01-14 14:30, Aleksandr Dezhin wrote: > On 01.01.2014 13:59, Paul J Stevens wrote: >> Aleksander, >> >> please try the attached patch. > I just tried to apply this patch, but it looks like it has not solved > the problem - imapproxy still can not reuse connections after 20-30 seconds. > If it helps, I can send logs with this patch.
Aleksander, imapproxy appears quite pathetic! I just did a simple benchmarker which does a login/logout cycle. hitting dbmail directly is an order of magnitude faster than hitting imapproxy. That seems quite surprising since imapproxy doesn't have to do any authentication, just hash and compare to the connection cache. But still, the numbers speak clearly: testing login/logout COUNT | 10 | 100 | 1000 ---------+--------+--------+--------- DBMail: | 0.0532 | 0.6054 | 6.9042 IMAPProxy| 0.3995 | 4.0095 | 40.0218 I'm adding the benchmark script I wrote to the master branch so you can test for yourself. http://git.dbmail.eu/paul/dbmail/tree/test-scripts/imapbench.py Note that for dbmail-2 using imapproxy made sense in order to reduce the concurrency pressure. But for dbmail-3 that doesn't fly any more. -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, github, linkedin * Premium Hosting Services and Web Application Consultancy * www.nfg.nl/i...@nfg.nl/+31.85.877.99.97 ________________________________________________________________ _______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
