Article ID: 319012 - View products that this article applies to.
This article was previously published under Q319012
When you use or view an ASP.NET page that includes a lot of client-side script, you may notice a significant decrease in performance. To detect this performance impact, monitor the "Request Execution Time" performance counter for ASP.NET.
NOTE: This performance problem only occurs on Microsoft Windows 2000 Server. This problem does not occur on Microsoft Windows XP.
To resolve this problem, obtain the latest service pack for Microsoft .NET Framework. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
318836The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/318836/EN-US/ )INFO: How to Obtain the Latest .NET Framework Service Pack
Date Time Version Size File name -------------------------------------------------------------- 21-Apr-2002 12:15 1.0.3705.258 192,512 Aspnet_isapi.dll 21-Apr-2002 12:10 19,332 Aspnet_perf.ini 21-Apr-2002 12:15 1.0.3705.258 24,576 Aspnet_regiis.exe 21-Apr-2002 12:15 1.0.3705.258 28,672 Aspnet_wp.exe 05-Apr-2002 12:07 8,709 Smartnav.js 05-Apr-2002 12:07 7,003 Smartnavie5.js 22-Apr-2002 00:39 1.0.3705.258 1,183,744 System_web.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft .NET Framework Service Pack 2 (SP2).
A typical large response to the client creates several smaller buffers in which the data sits before the data is sent to the client. For example, suppose that a response creates five buffers that are 1 kilobyte (KB), 3 KB, 28 KB, 4 KB, and 2 KB in size. The default message size is 32 KB. Therefore, because the total size of these buffers is greater than 32 KB, you must send the buffers one at a time to the client.
This fix tries to fill up 32 KB messages with these buffers so that you can send larger chunks to the client. The fix is significantly faster. Typically, this fix reduces the average time to last byte (TTLB) time by 200 milliseconds for any page with a response that is greater than 32 KB.
The following table outlines the TTLB improvements that occur with this fix. You can see similar improvements for other pages that have a response that is greater than 32 KB.
Collapse this tableExpand this table
Article ID: 319012 - Last Review: September 27, 2005 - Revision: 3.2