Am 25.07.2013 22:43, schrieb Paul J Stevens: > On 07/25/2013 04:26 PM, Reindl Harald wrote: > >> do you have a parallel-mtp-insert test somewhere? > > That is what test-scripts/testlmtp.py is for: concurrent connections to > lmtp. There is no specific test in there to insert the same message on > multiple concurrent connections, though. > > But then: having postfix or any other MTA open multiple connections to a > single dbmail-lmtpd process is possible, but makes no sense at all. > > dbmail-lmtpd is single-threaded, so in terms of throughput there is no > point. In fact, no process other than the multi-threaded dbmail-imapd > needs a max_db_connections greater than 1 (one)!
OK > I'll modify the default dbmail.conf to reflect that advise. OK > So: > > - Use a single connection database pool for lmtpd > - Don't let postfix open more than one single connection to dbmail-lmtpd > - If you need more than one lmtp channel, run dbmail-lmtpd from inetd > > Making dbmail-lmtpd scale better would require making it multi-threaded, > like imapd. A rather significant project in and of itself that's a different story the settings are the sam esince more than a year i am not sure what happens i have seen the "lost connection with 127.0.0.1[127.0.0.1] while sending end of data -- message may be sent more than once" *one* time due testing with a single 20 MB message and that was the primary reason for my "5000 messages with 1 MB" bulk script and after that did have no single issue i thought "well, nobody knows, i go in producton because it's unlikely to happen again"
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
