Philip Hazel wrote: > On Wed, 25 Oct 2006, gdub wrote: >> it could be a worth- >> while performance enhancement. > > I very much doubt it would be worthwhile. Most configs don't contain > many lines; as the file is frequently read, it will probably remain in a > main memory buffer. The amount of processor time to scan the data and > interpret it is very small. Exim is in any case disk-limited. Processor > time is not usually a limiting factor.
Our Exim configs are standardized across many machines and are pretty large as they handle a variety of scenarios. They make extensive use of macros and conditionals--we've now eliminated .includes entirely by implementing a config builder that runs before syncing configs across hosts. My concern was with all the spawning, Exim was doing the same computations over and over. >> for a listening daemon to share its >> configuration memory with its child >> processes? > > It does when it forks to receive a message. It cannot when it re-execs > in order to regain root privilege in order to deliver a message. That's good news. I just did a ps on a busy machine and about 70% of the exim processes are forks without execs. Since we only deliver via LMTP, could we configure Exim to not ever exec for delivery? Thanks for your help, -dub -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
