On Wed, 03 Apr 96 09:34:32 PST Jeff Heinen spake:
20000? You mean 20K? Woah.... Anyway, It think it would depend
on your server. Can it handle large lists? Also, you will have to
remove bounceing messages immeditally or it will fill up the mailqueue
and cause the list to be slower.
You may want to look into something like bulkmail, which sorts and
seperates the list into smaller sub-lists, spawning a sendmail proc
for each. More processes will make the machine work harder, but the
list should be sent out faster.
I've got a 15k list that I'm managing right now. The big problem with
the list is the amount of time that it takes to subscribe someone.. It
eats up nearly 2 minutes of CPU just subscribing a single user. Anyone
have any ideas about what the heck it's doing, and how to improve the
performance there? Here's an example from top:
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
1378 majordom 102 10 1428K 1612K run 1:29 74.32% 74.22% perl
If you do a trace on the process, you see this forever:
sigstack (0, 0xf7ff9e6c) = 0
sigcleanup () = 0
sigblock (0) = 0
sigstack (0, 0xf7ffc134) = 0
sigblock (0) = 0
sigstack (0, 0xf7ffa544) = 0
sigcleanup () = 0
sigblock (0) = 0
sigstack (0, 0xf7ffa544) = 0
sigcleanup () = 0
sigblock (0) = 0
sigstack (0, 0xf7ffa544) = 0
sigcleanup () = 0
sigblock (0) = 0
sigstack (0, 0xf7ffa544) = 0
sigcleanup () = 0
sigcleanup () = 0
sigblock (0) = 0
sigstack (0, 0xf7ff9e6c) = 0
sigcleanup () = 0
sigblock (0) = 0
sigstack (0, 0xf7ffc134) = 0
sigblock (0) = ^C
Any ideas?
Bryan
Follow-Ups:
References:
|
|
