Hello! The "request" means send mail request on the SMTP/SMTPS connection. The "performance result" means the speed per minutes for the mail sending.
So you're right about the following point. > Most critical parts from > performance point of view are your auth_http backend and your SMTP > backend. I understand that worker_connections and ssl_session_cache are seems to be useful as the performance of mail. Thank you for your answer:) Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > > On Tue, Feb 20, 2018 at 02:56:40AM -0500, Azusa Taroura wrote: > > > I’m trying to optimize mail-proxy. > > My performance test is 1 client sends many request to 1 nginx > server. > > [...] > > > Low cpu usage, but the performance result is not good. > > Do yoy know how to take full advantage of nginx? > > It is not clear what do you mean by "request", as there are no > requests in SMTP, and what do you mean by "performance result". > > In general, there is no need to optimize anything in nginx mail > proxy except very basic things like worker_connections and > ssl_session_cache if you use SSL. Most critical parts from > performance point of view are your auth_http backend and your SMTP > backend. > > -- > Maxim Dounin > http://mdounin.ru/ > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx Posted at Nginx Forum: https://forum.nginx.org/read.php?2,278656,278695#msg-278695 _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
