IIS

MSDN Webcast: Knee-Jerk Reactions to Proactive Solutions: Improved SharePoint Performance

dbottjer — Fri, 10 Jul 2009 21:34:18 GMT

What:	MSDN Webcast: Knee-Jerk Reactions to Proactive Solutions: Improved SharePoint Performance Attend this webcast to learn one dozen easy-to-implement performance tips for Microsoft Office SharePoint Server 2007. We discuss a wide range of topics from adjusting out-of-the-box settings to identifying memory leaks in custom code. We also describe several ways to proactively improve the user experience and squeeze more performance out of a SharePoint Server farm. Anyone currently designing a SharePoint Server implementation can benefit from this webcast.
When:	Friday, July 10, 2009 12:00 PM
Where:	MSDN Web Cast Live Meeting

Technorati Tags: Presentation,SharePoint Performance,MSDN Web Cast,ASP.NET MVP

Enable IIS 6 Compression for SharePoint

dbottjer — Tue, 14 Apr 2009 11:19:20 GMT

How to Enable IIS 6.0 Compression for SharePoint:

Microsoft’s Internet Information Server (IIS) has long support HTTP Compression. However, supporting and implementing compression are two different things. Many settings within IIS are easily configured from the IIS Admin GUI. Unfortunately, enabling and configuring compression is not supported through the GUI and requires editing the IIS Metabase. THe metabase can be edited manually or updated from a command prompt. The commands can be combine into the following script:

Script:

cd c:\inetpub\adminscripts

REM Turn On Compression
cscript adsutil.vbs set w3svc/filters/compression/parameters/HcDoDynamicCompression true
cscript adsutil.vbs set w3svc/filters/compression/parameters/HcDoStaticCompression true

REM Set Compression to High Level
cscript.exe adsutil.vbs set w3svc/filters/compression/gzip/hcdynamiccompressionlevel "9"
cscript.exe adsutil.vbs set w3svc/filters/compression/deflate/hcdynamiccompressionlevel "9"

REM IIS 6.0 Only

REM cscript.exe adsutil.vbs set w3svc/filters/compression/gzip/hcscriptfileextensions "css" "js" "asp" "exe" "axd" "aspx"
REM cscript.exe adsutil.vbs set w3svc/filters/compression/deflate/hcscriptfileextensions "css" "js" "asp" "exe" "axd" "aspx"

iisreset
pause

Recommendations:

File Extensions:

Consider Adding: “ascx”, “ashx”, “asmx” “xml”

Testing:

Test the various file extensions and compression levels. Perhaps start with a compression level of 7 to 8 or 9 after monitoring CPU utilization. The results of compression can be monitored using Fiddler.

Related Download Available:

Administration: From Knee Jerk Reactions to Proactive Solutions | A Dozen Tips for Improved SharePoint Performance (Presentation Slides)

Technorati Tags: Enable IIS 6 Compression

Loosing ASP.NET Session State in IIS6

dbottjer — Wed, 09 May 2007 19:25:00 GMT

Last year we deployed a new underwriting system. Since the Fall of 2006 we have been steadily releasing updates to the system. Supporting the large user-base of this application has required us to improve our debugging and performance monitor skills. For example, we have become huge fans of unit testing and made strides to better understand memory management and profiling. To protect the health of the application we needed to understand the recycling of application pools / worker processes.

Thoughts on Application Pool Recycling and Application Availability explains in detail how IIS6 is designed to gracefully transfer client connections to the new worker process. In general devising a health strategy and recycling application pools is a good idea. It is a bad idea to be overly aggressive in the recycling of Application Pools. For example, recycling an application pool every hour would be very aggressive. If application pool recycling is required that frequently I would profile the application's memory usage to determine how garbage collection is working. Perhaps objects aren't being disposed of in a timely manor. It is always a good idea to create a connection or instantiate an object as late as possible and dispose of them as soon as possible. Furthermore, forced Garbage Collection like the GC Collect method is not recommend b/c it can corrupt Garbage Collection Statistics.

When recycling an application pool for an application that maintains session state, the way in which the session state is maintained should be considered. For example, maintaining In-Process session state will result in a loss of session state when the Application Pool is recycled. As a result users may be forced to login to an application again.

Why do I lose ASP Session State on IIS6 further explains the loss of session state when maintaining state in-process. A better strategy may be to store session state out of process.

IIS Virtual Directory File Size Limit

Mon, 06 Mar 2006 15:29:00 GMT

I ran into an issue where cetain images served from a virtual directory, mapped to Network Attached Storage (NAS) via a UNC path would not display. After quite a bit of detective work I noticed that the images failing to display where those of about 600KB in size. If I resized the images under 200KB they dispalyed fine. I found some information on MSDN that states that IIS caches the remote files for faster delivery. Periodically, IIS poles the remote locations (UNC Paths) for file changes. I believe the following registry entry to be the cause:

MaxCachedFileSize
Registry Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters
Data Type: REG_DWORD
Default Value: 256 KB (262,144 bytes)
Controls the maximum size of cache files. The default is 256 KB if no value is present.

MaxCachedFileSize

Registry Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters

Data Type: REG_DWORD

Default Value: 256 KB (262,144 bytes)

Controls the maximum size of cache files. The default is 256 KB if no value is present.

.ASHX

dbottjer — Tue, 21 Jun 2005 07:45:00 GMT

Most .NET Web Applications are built using .ASPX and ASCX (User Controls) Files. However, ASP.NET provides an easy way to build HTTP Handlers via .ASHX Files. You might want to use HTTP Handlers when the output of your application isn't going to a web browser. For example, perhaps the output is xml that will be cosumed by some other type of client. HTTP Handlers implemented on IIS can be either ISAPI Extensions or ISAPI Filters. ISAPI Extensions are implemented as a windows dll and are the target of an HTTP Request. ISAPI Filters sit between the client and the web server intercepting all http requests.