FYI - I believe the issue was resolved. The Performance graph is now
back down to normal anyway, but I have not tested POP or other network
issues as I have taken the server down. But apparently the page file
was set too high. I reduced it down to 2GB (it was at 4GB - the
recommended size was 6GB!) and all is well. Apparently setting it too
high can cause an inordinate amount of I/O traffic. There is a registry
hack that can allow a page (swap) file to be higher than 4GB. But we
don't need it. In general if you have less than 2GB of RAM, use 1.5X
the size of your RAM, but if you have more than 2GB, use 2GB. But check
with your doctor before proceeding.
Kevin
Bruce Barnes wrote:
Dave,
Check your SQL server configuration. SQL server defaults "automatic" mode
and them enables SQL to use 100% of both memory and processor resources.
When installed on a server that's not a DEDICATED SQL machine, it's wise to
back off both the memory and processor resources available to SQL to a max
of 50% of both. Depending on the memory you have installed on the new
machine, you might also want to back it down ever further.
Remember, too, that both SQL 2005 and Windows Server 2003 require
significantly more memory than previous versions of either required.
Good luck in resolving this.
Bruce Barnes
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Marchette
Sent: Saturday, June 03, 2006 23:13
To: [email protected]
Subject: RE: [IMail Forum] new server, much slower
Kevin,
1 Can you define 'Mail delivery much slower' more precisely? Are you
referring to mail delivery loop times, send, receive, general speed issues,
etc? Do the actual Imail logs reveal anything of interest? In older
versions, we'd see 'stack connect failures' related to slow delivery times.
Not sure what you may see on recent versions.
2 The 'Windows cannot obtain the domain controller name' error is likely
due to the fact that you are not using an AD enabled DNS. If your server
is joined to a domain and trying to AD authenticate for any
reason(specifically, SQL permission queries to the DC), and if your websites
and the Imail app are trying to use SQL for any reason, this could cause
significant speed\lookup issues. Also, there is a documented issue with
Imail\2003\DNS, but I seem to think it is was function and not performance
related.
3 What are your Performance Monitor stats? Any disk, proc or memory
saturation occurring?
4 Any real-time AV running on your box, perhaps scanning more than it
should?
I'd first try utilizing your own DNS. DNS is highly critical to mail
delivery performance and should not be done remotely.
Dave
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kevin Rogers
Sent: Friday, June 02, 2006 8:12 PM
To: [email protected]
Subject: [IMail Forum] new server, much slower
We recently moved Imail to a new server and mail delivery is much slower
now. The old and new server are both running 8.21. The old server was
running SQL Server 2000, the new one has SQL Server 2005. Old server
was running Windows 2000 Server, new one has 2003 Server Small
Business. The old one had its own local DNS server setup, but the new
one does not have it yet, so we're using Covad's DNS servers and when
pinging them, they seem fine (little latency). I contacted Covad and
they say our network traffic is no where near peak so we should be fine
there.
They both are using Declude 1.81, sniffer, f-prot and WorkgroupShare
(not Imail's version) for Outlook sharing.
It also appears as though the few websites we are hosting on the same
server are also much slower.
The new server has a much faster processor and 4gb of RAM, so I'm
thinking it's not the hardware (could be the NIC). Could it be IIS or
SQL Server? If it were just the mail delivery, I would think Imail, SQL
Server or the NIC card. But since the web sites are also slower, does
that mean Imail is not the problem (so I'm left with it being SQL
Server, NIC, or IIS)?
One error I get in the Event Viewer is this:
Windows cannot obtain the domain controller name for your computer
network. (An unexpected network error occurred. ). Group Policy
processing aborted.
and this:
Error: The Template Persistent Cache initialization failed for
Application Pool 'DefaultAppPool' because of the following error: Could
not create a Disk Cache Sub-directory for the Application Pool. The data
may have additional error codes..
Kevin
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/
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/
