On Wed, 25 Oct 2006, gdub wrote:
> Since exim reads and processes its
> config file so often (please correct
> me if I'm wrong), it could be a worth-
> while performance enhancement. First
> step would be to profile process startup.
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.
> Alternatively, would it be possible
> 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.
--
Philip Hazel University of Cambridge Computing Service
Get the Exim 4 book: http://www.uit.co.uk/exim-book
