[Mailman-Users] Large List Considerations

[Jon Carnes]

On Thu, 2004-02-05 at 18:06, Bernd Petrovitsch wrote:
> On Thu, 2004-02-05 at 22:28, Jon Carnes wrote:
> [...]
> > If however you find that messages spend a long time in the queue before
> > being processed (or web-access to the list configuration is very slow to
> > load) then you might want to consider putting aside some ram for use as
> > a disk.  You can copy your ~mailman/lists/... to this RAM drive and
> > mount it over the ~mailman/lists (then startup Mailman).  Access to the
> > lists and configuration will then be much faster.
> > 
> > Note: the RAM drive *must* be at least twice the size as the data stored
> > in it, so that Mailman can make backup copies of the config files while
> > doing changes.
> 
> Which raises the question if simply adding the RAM to the system thus
> increasing the disk cache (and not dedicated to just one part of the app
> and - given the above description - wasting 50% of it almost completely,
> not considering fault-tolerance and similar) won't be as good (if not
> batter)´?
> 
> 	Bernd

Alas, there is a whole lot of writing going on that just adding RAM does
not address. If all Mailman did was read the list from the same process
each time, then adding RAM would be the best bet.

Jon Carnes