Re: [Exim] split_spool_directory overhead

Top Page
Delete this message
Reply to this message
Author: Dave C.
Date:  
To: Philip Hazel
CC: Sheldon Hearn, exim-users
Old-Topics: Re: [Exim] split_spool_directory overhead
Subject: Re: [Exim] split_spool_directory overhead
On Mon, 15 Oct 2001, Philip Hazel wrote:

> On Mon, 15 Oct 2001, Sheldon Hearn wrote:
>
> > 2) Exim queue runners' memory requirements are directly proportional to
> >    the size of the largest spool directory.

>
> Yes, that's true. I'd forgotten to point that out.
>
> > Do you think point 2 is unavoidable, or is it just the result of poor
> > memory management in an area that you never imagined would become
> > important?
>
> It's unavoidable without an entirely different way of doing queue runs.
> (Basically, Exim sucks the queue - i.e. the list of files - into memory
> at the start, and then processes it. When the spool directory is split,
> it does this one sub-directory at at time.)



I have a question on this - do queue runners pick a random subdirectory
to process, or do they run them in order?

Eg, if I start 5 queue runners, will they all start with the same
subdir, or different ones?

I suspect (and am hoping) they they are random. This is Exim 3.3x, btw..