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
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
