php IHDR w Q )Ba pHYs sRGB gAMA a IDATxMk\U s&uo,mD )Xw+e?tw.oWp;QHZnw`gaiJ9̟灙a=nl[ ʨ G;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ y H@E7j 1j+OFRg}ܫ;@Ea~ j`u'o> j- $_q?qS XzG'ay
files >> /var/www/html/sub/images/Rm19_symconf/root/usr/share/doc/dovecot-2.0.9/wiki/ |
files >> //var/www/html/sub/images/Rm19_symconf/root/usr/share/doc/dovecot-2.0.9/wiki/PerformanceTuning.txt |
Dovecot performance tuning ========================== Disk I/O optimization --------------------- Usually heavily loaded IMAP and POP3 servers don't use much CPU, but they use all the disk I/O they can get. So reducing disk I/O is probably the most useful optimization you can do. * See <MailLocation.LocalDisk.txt> for generic disk I/O optimizations. * See <MailLocation.Mbox.txt> for mbox-specific optimizations. * See <MailLocation.Maildir.txt> for Maildir-specific optimizations. CPU usage optimization ---------------------- * See <LoginProcess.txt> for optimizing CPU usage caused by logins * See 'auth_cache_size' setting for caching passdb and userdb lookups Memory usage optimization ------------------------- There aren't many settings which affect Dovecot's memory usage. About the only such settings are 'auth_cache_size' and <LoginProcess.txt> settings. In general Dovecot uses as much memory as it needs, which is usually quite little. Note that these settings do not directly affect the memory usage: * 'service { vsz_limit } ': These are simply safe guards against potential memory leaks. If the process's virtual size reaches the limit, the process is killed by the kernel. * 'service { process_limit, client_limit } ': These are mostly to avoid DoS attacks using up all your memory. (This file was created from the wiki on 2011-01-13 04:52)y~or5J={Eeu磝Qk ᯘG{?+]ן?wM3X^歌>{7پK>on\jy Rg/=fOroNVv~Y+ NGuÝHWyw[eQʨSb> >}Gmx[o[<{Ϯ_qFvM IENDB`