X hits on this document





23 / 30

Microsoft® Windows Server™ 2003 White Paper

As shown in this figure, you can see that IIS does not cache any ASP files by default. This forces the client browser to query the server for a new (or updated) page at each request. Although this strategy saves disk space on the client, it increases application response time. However, the client is assured of obtaining the most current version of the page or pages.

You can use the cache options to improve performance of the application. You can either force the cache to memory on the server or limit the amount of files cached in memory and force the rest to disk. If you force them to disk, then you might consider setting up the cache directory on a fast disk.

There are also server settings that can impact the server’s performance. For instance, there are certain ASP settings that change the server’s behavior to one that will not scale as well. Tweaking these options can make a big difference on your server, especially if you are running ASP.NET applications only and not any ASP applications. This information is found in the Performance Settings topic in the IIS 6 Documentation.

Another important property, Enable Direct Metabase Edit, allows changes to the metabase while IIS is running. This setting allows you to make edits that affect scalability while the servers are in production if necessary. You can change this on the property page for the IIS server as shown below.

Implementing a Scalable Architecture21

Document info
Document views53
Page views53
Page last viewedFri Oct 28 21:51:39 UTC 2016