[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

3626.0. "Fetcher Performance: 2-3 Messages/Minute!" by MIMS::BEKELE_D (My Opinions are MINE, MINE, all MINE!) Sun Dec 05 1993 00:51

Would appreciate any help on the following:
 
A customer has:

	VAX 7610 
	VMS 5.5-2 
	ALL-IN-1 V2.4, 
	Message Router V3.2, and Multinet V3.2 

The problem is 5000+ incoming SMTP messages/day have resulted in a 12 
hour (and growing!) backlog of unfetched messages.

The cpu has idle time, I/O is low and no DECnet problem is detected.
The customer had been advised to (look into the obvious areas: fragmentation,
small bucket size for postmaster docdb, too many ALL-IN-1 accounts having
too many unread messages, accounts with problem auto-forwarding, ect.
The fetcher is still processing only 2-3 messages/minute! 

Any word of wisdom?
Thanks!

Dan
T.RTitleUserPersonal
Name
DateLines
3626.1postmaster's DAF?IOSG::DAVISMark DavisWed Dec 08 1993 16:1314
    
    You say they checked the Postmaster DOCDB - did they also check the
    Postmaster DAF as this will slow down the fetcher if the bucket size is
    too small.
    
    Also if the files along the way such as the Pending file and the
    postmasters DAF and DOCDB have not been converted for some time this
    might introduce some slowness into the porcess.
    
    The only other thing that I can think of that you haven't mentioned
    that might be slowing down the fetcher is the sending of very large
    messages.                                      
    
    			Mark
3626.2Happy endingMIMS::BEKELE_DMy Opinions are MINE, MINE, all MINE!Sun Dec 12 1993 04:4918
    
    Mark,
    
    Thanks for the help!  The main cause turns out to be mis-configuration
    of Message Router:  1) back in September the customer had moved MR away 
    from SYS$SYSDEVICE but they failed to change the device name for MRNET &
    MB$WATCH UAF records 2) they had also failed to do a "recover" 3) they
    had default configuration and 5,000/day Internet messages were being 
    pushed into only two directories that grew to over 400blocks themselves.
    Once directory caching was lost for MR$NBS the performance degradation
    got worse.
    
    After corrective actions were taken (added [.MSG3], [.MSG4], [.MSG5]
    among others) about 12 messages/minute are now being fetched.  The rate 
    should go up when all MSG*.DIR files fall below 128blocks.
    
    Regards,
    Dan