With this many subscribers, have you thought about interfacing Mj with
a database like MySQL? This would be faster, and instead of having
to regenerate the db file from a huge textfile every time there's an
(un)zubscribe, you could issue a single insert/delete command to the
SQL server. OTOH, you'd then be creating a dependency on another
piece of software.
Omar
On Tue, Jul 07, 1998 at 08:45:12PM -0700, Chuq Von Rospach wrote:
>
> With majordomo, large lists are pretty straightforward. There are a
> couple of places that'll bite you:
>
[...]
>
> This is one weakness in majordomo. I've looked at replacing the
> subscriber list with a dbm file, and then teaching bulkmailer and other
> routines like which/who to read from it, so that updates are closer to
> simultaneous, but haven't done that yet. That's a future.... but since
> I expect some lists to be pushing 300,000 by year end, I think I'll
> need it. Sequential reading and writing of a flat file just doesn't
> scale, and there's only so much you can do with faster hardware.
Follow-Ups:
References:
|
|
