Here's a tidbit from the white paper:
"Note: Selecting the "Run in separate memory space" option is generally not recommended outside of ASP development. Enabling this option causes excessive overhead by way of duplicate change/notify requests for each process on the remote machine specified in the Network Directory field. This is true not only for NetApp filers, but also for any machine that IIS accesses in this manner. IIS 5 presents a third option (now under the heading of Application Protection) called medium (pooled). Since this pools processes together rather than creating a separate process for each one, it doesn't cause as much overhead on the remote machine."
http://www.netapp.com/tech_library/3078.html
-----Original Message----- From: Andrew Smith [mailto:ajs@dca.net] Sent: Monday, March 19, 2001 12:46 PM To: theffron@wisedata.com Cc: 'toasters@mathworks.com ' Subject: Re: ASP caching
Hello,
We have worked around this by disabling ASP caching on those vhosts where it is requested. Once the customer finishes development work, we re-enabling caching to keep the load down on our filer.
The way to do this is:
- Open the Properties window of the vhost in question in the IIS manager - Under 'Home Directory' set the Application Protection to 'High' - Press 'Configuration' and uncheck 'Cache ISAPI applications'.
This works for us. We've found that if we disable 'Cache ISAPI applications' for the entire web server, the load on our filer and out web servers spikes way, way up. ISAPI caching dramatically increases performance. I just wish that IIS was smart enough to look at something as simple as the 'changed date' on a file to see if it should reload it into cache.
On Mon, 19 Mar 2001, Jean-Christophe Smith wrote:
We have a cluster of Windows 2000 servers running IIS 5.0, content lives
on
a NetApp F720 running OnTap Release 5.3.7R2. Our customers use FTP to
upload
their web pages.
IIS is caching ASP(active server pages), customers will make changes to their ASP files and try to view them(view IIS) and they see the older
pages.
I read about this issue entitled "5.3 Active Server Page Caching" in the NetApp document "Integrating a NetApp Filer with Microsoft IIS". I understand it is an issue with CIFS change/notify events and the way IIS
was
designed.
Does anybody know a way of fixing this? or maybe way to increase the change/notify events, or...
For now, we have to restart IIS when changes are made.
Maybe I could write a program to manually induce change/notify events?
Thanks, Jean-Christophe Smith jsmith@publichost.com VitalStream.com