CRS: Poor TCP/IP Performance with Small Sends
Article ID: 179279
Article Last Modified on 3/11/2005
APPLIES TO
- Microsoft Commercial Internet System 1.0 Service Pack 2
- Microsoft Content Replication System
- Microsoft Site Server 2.0 Standard Edition
This article was previously published under Q179279
SYMPTOMS
When you are doing multiple sends of less than the Maximum Transmission
Unit (MTU), you may see poor performance. On an Ethernet network, the
default MTU for TCP/IP is 1,460 bytes. TCP can coalesce the two small sends
into one larger packet. This concept of collecting small sends into larger
packets is called Nagling.
Content Replication Server (CRS) in Microsoft Commercial Internet System
(MCIS) 1.0 and Site Server 2.0 has Nagling enabled by default. The registry
key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CRS\DisableNagle :REG_SZ: Yes/No
does not function properly in MCIS 1.0 and Site Server 2.0 CRS.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Commercial
Internet Server version 1.0 and Site Server version 2.0. This problem has
been corrected in the latest U.S. Service Pack for Site Server 2.0 Service
Pack 1. For information on obtaining the Service Pack, query on the
following word in the Microsoft Knowledge Base (without the spaces):
MORE INFORMATION
Nagling is off by default in Site Server 2.0 SP1. Nagling is a large
performance hit and greatly increases the time it takes for a replication
to complete.
See also RFC 1122.
Keywords: kbbug kbfix kbother KB179279