- SCSI Hard Drives. No partitioning. Defrag by Diskeeper.

 - Mailboxes are using 4GB of total disk space. only 120 users take
advantage of our "masochistic generosity" and use more than 10MB.

 - The spool contains between 500 and 800 files on any given day, with no
files older than 1 week.

 - Network Adapter was switched to a 3com 3C905CX-TX-NM 4 days ago. The
onboard GigE Broadcom adapters were disabled in both Windows and BIOS.

 - When processor utilization goes to 100%, the primary culprit is SMTPD
(10% to 40%) and between 10 and 20 SMTP processes (each between 0% and 20%).
The 100% processor is most often triggered by a 120 user mailing list that
receives about 50 posts per day.

 - can you give more explicate instructions on the looping batch file.

Thanks,

Ted

-------------------------------

----- Original Message -----
From: "Len Conrad" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 14, 2003 9:54 AM
Subject: Re: [IMail Forum] Imail processor problems - continued


>
> >  - Dell PowerEdge 2650 - 2.0 Ghz Xeon - Raid 1 (2x72GB)
>
> ATA or SCSI?
>
> what about the all important partitioning?
>
> >  - 1GB Ram
> >  - 1500 domains
> >  - 3700 mailboxes
>
> ... not really very much at all
>
> >  - 100MB max mailbox size
>
> Totally nutz, but whatever.  This masochistic generosity, if exploited
> by  your users, requires that you put the mailbox storage on a separate
> controller, preferably caching, and to be continually defragged.  And if
> some users actually run 100 MB mailboxes, give them one month credit and
> tell them find anonther ISP.  :))
>
> >  - Web messaging Enabled and actively used with KWM Templates
>
> Sandy says this can be greatly accelerated by segregating the webmail
> workspace to a separate partition, but see below.
>
> >  - 50,000 SMTPD Connections Daily
>
> less than one/second, not much at all.
>
> >  - 40,000 SMTP Local Deliveries Daily
> >  - 12,000 SMTP Senders Remote Daily
> >  - 38,000 SMTP Senders Local Daily
> >  - 175,000 Pop Logins Daily
> >  - 700 Web Logins Daily
>
> ah, good.  primarily a POP server, so why the 100 MB of mailbox?  Don't
> your users empty their mailboxes (don't "leave mail on server") with every
> mailbox check?
>
> What are the actual max and avg .mbx file sizes?
>
> >Given the stats above, I see no outward reason that Imail should be
> >performing so poorly.
>
> We can't conclude that without detailed spec of your disk and partition
> allocations, as well as spool/ cleaning and defragging practices.
>
> >Our only real conclusion has been that there must be a
> >hardware compatibility issue that is preventing the Imail software from
> >multitasking properly.
>
> hardware has been fixed with the 1 GB adaptor change, and the 10054 errors
> need to be fixed.
>
> If you can't run mtr on a *nix box on the same subnet as your Imail box:
>
> To try to see where the TCP problems may be occurring, run on the Imail
box
> this command in a looping batch file :
>
> pathping -n -p 1 -q 200 -w 200 ip.ad.re.ss >> \path\to\pp.txt
>
> ... where ip.ad.re.ss is an IP at other end of your WAN link or somewhere
> closer, but esp on the same route used by your subscribers to access
Imail.
>
> You might also pathping between the imail box and your dial-up access box,
> if you have one.
>
> You might see a some packet loss on IP(s) local to your shop that would
> indicate where to start changing stuff.
>
> When your CPU pegs (seems you have no problem with observing that), what
> processes are hogging the CPU, and what is the disk r/w activity during
> that period?
>
> Len
>
>
> To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
> List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
> Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
>


To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/

Reply via email to