| 1 |
The process count keeps growing! |
| 2 |
================================ |
| 3 |
|
| 4 |
If you notice that your imapd process count continues to grow and never decreases, there are a number of options which may be affecting it. |
| 5 |
|
| 6 |
1. Reuse count |
| 7 |
-------------- |
| 8 |
|
| 9 |
By default, imapd processes will remain alive for 250 new connections before shutting down. Setting this to a lower value will reduce the amount of time unused processes hang around. There is a tradeoff between startup/shutdown overhead and process longevity. |
| 10 |
|
| 11 |
The use setting is the **- U** argument to :cyrusman:`imapd(8)`. |
| 12 |
|
| 13 |
2. Maximum child count |
| 14 |
---------------------- |
| 15 |
|
| 16 |
By default, Cyrus is allowed to spawn a limitless number of child imapd processes. To control this growth, adjust the **maxchild** option in :cyrusman:`cyrus.conf(5)`. |
| 17 |
|
| 18 |
3. Clean up connections that are no longer in use |
| 19 |
------------------------------------------------- |
| 20 |
|
| 21 |
While POP connections are short lived, IMAP connections can be long lived. And then there are processes trying to listen to a client that's no longer alive. |
| 22 |
|
| 23 |
Setting **tcp_keepalive** option in :cyrusman:`imapd.conf(5)` to **1** can be used to test if connections are still alive. The operating system will send an ACK packet every so often (every 2 hours by default on Linux) which tests if the TCP endpoint is still reachable. |
| 24 |
|
| 25 |
The other **tcp_keepalive_** options help control how and when the test occurs. |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
|