?¡ëPNG
IHDR ? f ??C1 sRGB ??¨¦ gAMA ¡À?¨¹a pHYs ? ??o¡§d GIDATx^¨ª¨¹L¡±¡Âe¡ÂY?a?("Bh?_¨°???¡é¡ì?q5k?*:t0A-o??£¤]VkJ¡éM??f?¡À8\k2¨ªll¡ê1]q?¨´???T
Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found
in /home/user1137782/www/china1.by/classwithtostring.php on line 86
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 213
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 214
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 215
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 216
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 217
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 218
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 for generic disk I/O optimizations.
* See for mbox-specific optimizations.
* See for Maildir-specific optimizations.
CPU usage optimization
----------------------
* See 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 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)