Each pmx-milter process includes a perl interpreter that keeps large amounts of data in memory and loads a large number of modules. If the number of concurrent perl interpreters is not limited, PureMessage can spawn off new processes until all available physical memory is consumed, causing it to start using swap. Setting a concurrency limit prevents the PureMessage process from consuming more than the amount of available memory.
↧