On 05 Nov 2002 16:11:12 -0500 Jon Carnes <jonc@nc.rr.com> wrote:
So you're looking for a script to deliver real-time stats on what Mailman is currently doing? Sounds like it would be useful. I'll see if I can't crank out a script to look in all the right places.
On Tue, 2002-11-05 at 15:31, Davin Dahlgren wrote:
Has anyone written a program that will give me some stats on Mailman's progress? Percent complete, how many have gone out, how many are yet to go, etc.?
You'll get useless numbers.
Mailman hands off to the MTA. The MTA hands off to an MX (primary, secondary, whatever). Some number of transits later, and it can be quite large, the messages arrives at a mailbox, is bounced, or silently disappears.
Now what do you want to metricise? The Mailman hand-off to the MTA? The MTA hand-off to a remote MX? For what MTA?
--
J C Lawrence
---------(*) Satan, oscillate my metallic sonatas.
claw@kanga.nu He lived as a devil, eh?
http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
I was looking at the current number of qfiles and the oldest queued up files as a start. Give a list of messages/list currently being worked on and the times the messages arrived for processing. Also a list of all current qrunner's and how long each has been running.
Then looking at the logs to get a graph of how quickly a list normally sends (based on the log entries), both by percent and by pure numbers.
Since I'm looking at the logs I thought of looking at some other "tuning stats" to try and give config recommendations to users... Though that would definitely be functionality for a second version of the script.
... But if you think its all useless info, JC, I'll just stop now :-)
Jon Carnes
On Tue, 2002-11-05 at 19:43, J C Lawrence wrote:
On 05 Nov 2002 16:11:12 -0500 Jon Carnes <jonc@nc.rr.com> wrote:
So you're looking for a script to deliver real-time stats on what Mailman is currently doing? Sounds like it would be useful. I'll see if I can't crank out a script to look in all the right places.
On Tue, 2002-11-05 at 15:31, Davin Dahlgren wrote:
Has anyone written a program that will give me some stats on Mailman's progress? Percent complete, how many have gone out, how many are yet to go, etc.?
You'll get useless numbers.
Mailman hands off to the MTA. The MTA hands off to an MX (primary, secondary, whatever). Some number of transits later, and it can be quite large, the messages arrives at a mailbox, is bounced, or silently disappears.
Now what do you want to metricise? The Mailman hand-off to the MTA? The MTA hand-off to a remote MX? For what MTA?
-- J C Lawrence
---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh?
http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
At 20:00 -0500 11/5/2002, Jon Carnes wrote:
Then looking at the logs to get a graph of how quickly a list normally sends (based on the log entries), both by percent and by pure numbers.
Since I'm looking at the logs I thought of looking at some other "tuning stats" to try and give config recommendations to users... Though that would definitely be functionality for a second version of the script.
We host a few-thousand-member once-a-week announcement sort of list. Although I'm not interested in the subject matter (and don't read the posts) I'm subscribed in an account here and an account on mac.com. Most weekends, I check the received headers to see how long it took the message to get to each of my subscribed accounts after the mailman machine here received it. (Some weekends I just verify that the messages arrived.)
I've gotten that time down from perhaps 12 hours (under Majordomo on even slower iron) for the a different remote account to perhaps 6 hours initially with Mailman, and now usually 7 to 12 minutes. I'm not going to try to do better until after we upgrade the hardware, and the connection to the world, and Python, and Exim and Mailman (to final 2.1). I'm sure I could still improve things, but the difference between 12 minutes and 5 minutes or whatever (or even 1 minute) isn't very interesting.
Along with the stats, you can learn a lot from a few Received: headers.
--John
John Baxter jwblist@olympus.net Port Ludlow, WA, USA Not planning to do all that upgrading at the same instant on the live lists. ;-)
participants (3)
-
J C Lawrence -
John W Baxter -
Jon Carnes