|
Related Topics:
| ASP CLASSIC UNDER IIS 6 - hi to all. i have ASP based web site wich works corecctly under win 2000 pro ( iis 5) but i dosnt work in win 2003 server (iis6 ) i have been enabled ASP server extension ( changed it from prohabit to allowed) but i still have a problem with
Classic ASP and IIS 6.0 - I keep getting the 404 error, page not found, whenever I try to access my classic ASP website on IIS 6. The ASP.NET websites work fine -- any ideas? Thanks, Matt
Migrate 'classic' ASP from IIS 5 -> 6 - Hi - I've found on the MS website an article about migrating from IIS 4 to IIS 6 but what about IIS5 to IIS6 ? I've got a ASP which in future may need to go on a Windows 2003 box - can anyone help with a reference to such an article ? thanks ..
Running ASP Classic on iis 6.0 - I'm moving several existing from a Windows 2000, IIS 5.0 box to a Windows 2003, iis 6.0 box. I have no interest in upgrading the to ..Net. These apps work fine as is on the 2000 box. But in 2003, it seems that I'm running into..
IIS 5.1 on XP Pro cannot serve ASP classic - Hi all, I just got a new laptop, Windows XP Pro SP2. I installed IIS 5.1 using Windows I installed Visual Studio 6 SP6 and Visual Studio .Net (I need both of them). Exact same setup was working fine on my old laptop. On the new..
|
|
|
Next: IIS: Can not write to inetpub/wwwroot
|
| Author |
Message |
External
Since: Aug 25, 2006
Posts: 4
|
(Msg. 1) Posted: Fri Aug 25, 2006 10:25 am
Post subject: Classic ASP & IIS 6
Archived from groups: microsoft>public>inetserver>iis (more info?)
|
|
|
I'm hoping you could help me out determining whether IIS 6's new features
apply to Classic ASP or just .Net based apps.
IIS 6's features I want for my Classic ASP app are:
detecting memory leaks,
access violations,
recycling processes,
managing resources (e.g. worker process isolation mode and kernel-level
request queuing)
My Plan:
I plan to migrate a classic ASP app to IIS 6 in hopes of using IIS 6's
features above. My plan is to simply copy & paste my ASP pages into IIS 6 and
be done with it. However, I'm wondering if I need to migrate my code to
ASP.NET in order to get the new IIS 6 features, or whether these features are
enabled at the application pool regardless of code base.
What are your thoughts?
--
Edgar |
|
| Back to top |
|
 | |
External
Since: Aug 25, 2003
Posts: 2419
|
(Msg. 2) Posted: Sun Aug 27, 2006 1:30 am
Post subject: Re: Classic ASP & IIS 6 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
IIS6's new features apply at the application pool level regardless of
codebase. Thus, it applies to ASP, ASP.Net, PHP, Perl, JSP, etc.
However, just because the feature applies does not mean it actually "works"
with a given codebase. That depends on the codebase itself.
I'd like to clarify the behavior of the IIS6 features you listed:
- IIS6 does not detect memory leaks. It only detects amount of memory used
by a process and recycles at a threshold
- IIS6 does not do anything about access violations other than letting them
happen and restarting a new w3wp.exe afterwards. If the AV happens too
frequently, IIS will stop the Application Pool
- Recycling Processes happen depending on health monitoring metrics
- Managing Resources - Not certain what you are referencing
Your ASP application should just work on IIS6. It may be able to take
advantage of the new IIS6 features. It may be broken by the new IIS6
features. You will have to describe the application and your settings in
more detail to determine the actual answer.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"mresanchez" <mresanchez RemoveThis @donot-spam.com> wrote in message
news:67FADCF2-2DF1-422E-B17B-4A8B58643416@microsoft.com...
> I'm hoping you could help me out determining whether IIS 6's new features
> apply to Classic ASP or just .Net based apps.
>
> IIS 6's features I want for my Classic ASP app are:
> detecting memory leaks,
> access violations,
> recycling processes,
> managing resources (e.g. worker process isolation mode and kernel-level
> request queuing)
>
> My Plan:
> I plan to migrate a classic ASP app to IIS 6 in hopes of using IIS 6's
> features above. My plan is to simply copy & paste my ASP pages into IIS 6
> and
> be done with it. However, I'm wondering if I need to migrate my code to
> ASP.NET in order to get the new IIS 6 features, or whether these features
> are
> enabled at the application pool regardless of code base.
>
> What are your thoughts?
>
> --
> Edgar |
|
| Back to top |
|
| |
External
Since: Aug 25, 2006
Posts: 4
|
(Msg. 3) Posted: Mon Aug 28, 2006 8:23 am
Post subject: Re: Classic ASP & IIS 6 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Hi David,
In this particular case, the ASP application hosts files which users can
download.
We host large files ranging from 50-700MB+ size. Some of the "largest" and
"most" requested files, we cached in IIS 5 via this registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters
"MaxCachedFileSize"=dword:3b9aca00 // So the server(s) is configured to
cache files that are up to 1000000000 bytes in size within the Inetinfo
process.
// The default
for MaxCachedFileSize is 256kb
"ObjectCacheTTL"=dword:ffffffff // The cache scavenger is
disabled...cached data will remain in memory until overwritten
We're hoping IIS6/Win2k3 may help automate the "cache clean-up", and
IIS-application pool recycling. Right now, we do this manually whenever the
site becomes unavailable.
--
Edgar
"David Wang [Msft]" wrote:
> IIS6's new features apply at the application pool level regardless of
> codebase. Thus, it applies to ASP, ASP.Net, PHP, Perl, JSP, etc.
>
> However, just because the feature applies does not mean it actually "works"
> with a given codebase. That depends on the codebase itself.
>
> I'd like to clarify the behavior of the IIS6 features you listed:
> - IIS6 does not detect memory leaks. It only detects amount of memory used
> by a process and recycles at a threshold
> - IIS6 does not do anything about access violations other than letting them
> happen and restarting a new w3wp.exe afterwards. If the AV happens too
> frequently, IIS will stop the Application Pool
> - Recycling Processes happen depending on health monitoring metrics
> - Managing Resources - Not certain what you are referencing
>
> Your ASP application should just work on IIS6. It may be able to take
> advantage of the new IIS6 features. It may be broken by the new IIS6
> features. You will have to describe the application and your settings in
> more detail to determine the actual answer.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
>
> "mresanchez" <mresanchez.RemoveThis@donot-spam.com> wrote in message
> news:67FADCF2-2DF1-422E-B17B-4A8B58643416@microsoft.com...
> > I'm hoping you could help me out determining whether IIS 6's new features
> > apply to Classic ASP or just .Net based apps.
> >
> > IIS 6's features I want for my Classic ASP app are:
> > detecting memory leaks,
> > access violations,
> > recycling processes,
> > managing resources (e.g. worker process isolation mode and kernel-level
> > request queuing)
> >
> > My Plan:
> > I plan to migrate a classic ASP app to IIS 6 in hopes of using IIS 6's
> > features above. My plan is to simply copy & paste my ASP pages into IIS 6
> > and
> > be done with it. However, I'm wondering if I need to migrate my code to
> > ASP.NET in order to get the new IIS 6 features, or whether these features
> > are
> > enabled at the application pool regardless of code base.
> >
> > What are your thoughts?
> >
> > --
> > Edgar
>
>
> >> Stay informed about: Classic ASP & IIS 6 |
|
| Back to top |
|
| |
External
Since: Aug 25, 2003
Posts: 2419
|
(Msg. 4) Posted: Tue Aug 29, 2006 2:56 am
Post subject: Re: Classic ASP & IIS 6 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Are the files downloaded via the ASP application, or as static resources
served by IIS? In other words, are the downloads served as either:
http://localhost/Application.asp?id=FileName.ext
http://localhost/Downloads/FileName.ext
I ask for this distinction because it directly affects necessary
configuration and optimizations.
On IIS6, you want to take advantage of the kernel mode response cache for
the same chores because it will offer up to 10x performance improvement. It
is not configured with those registry keys at all.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"mresanchez" <mresanchez.RemoveThis@donot-spam.com> wrote in message
news:5F81DD6C-8315-4408-8EF5-36CF5A3DF107@microsoft.com...
> Hi David,
>
> In this particular case, the ASP application hosts files which users can
> download.
>
> We host large files ranging from 50-700MB+ size. Some of the "largest"
> and
> "most" requested files, we cached in IIS 5 via this registry:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters
>
> "MaxCachedFileSize"=dword:3b9aca00 // So the server(s) is configured to
> cache files that are up to 1000000000 bytes in size within the Inetinfo
> process.
> // The default
> for MaxCachedFileSize is 256kb
> "ObjectCacheTTL"=dword:ffffffff // The cache scavenger is
> disabled...cached data will remain in memory until overwritten
>
> We're hoping IIS6/Win2k3 may help automate the "cache clean-up", and
> IIS-application pool recycling. Right now, we do this manually whenever
> the
> site becomes unavailable.
>
> --
> Edgar
>
>
> "David Wang [Msft]" wrote:
>
>> IIS6's new features apply at the application pool level regardless of
>> codebase. Thus, it applies to ASP, ASP.Net, PHP, Perl, JSP, etc.
>>
>> However, just because the feature applies does not mean it actually
>> "works"
>> with a given codebase. That depends on the codebase itself.
>>
>> I'd like to clarify the behavior of the IIS6 features you listed:
>> - IIS6 does not detect memory leaks. It only detects amount of memory
>> used
>> by a process and recycles at a threshold
>> - IIS6 does not do anything about access violations other than letting
>> them
>> happen and restarting a new w3wp.exe afterwards. If the AV happens too
>> frequently, IIS will stop the Application Pool
>> - Recycling Processes happen depending on health monitoring metrics
>> - Managing Resources - Not certain what you are referencing
>>
>> Your ASP application should just work on IIS6. It may be able to take
>> advantage of the new IIS6 features. It may be broken by the new IIS6
>> features. You will have to describe the application and your settings in
>> more detail to determine the actual answer.
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> "mresanchez" <mresanchez.RemoveThis@donot-spam.com> wrote in message
>> news:67FADCF2-2DF1-422E-B17B-4A8B58643416@microsoft.com...
>> > I'm hoping you could help me out determining whether IIS 6's new
>> > features
>> > apply to Classic ASP or just .Net based apps.
>> >
>> > IIS 6's features I want for my Classic ASP app are:
>> > detecting memory leaks,
>> > access violations,
>> > recycling processes,
>> > managing resources (e.g. worker process isolation mode and kernel-level
>> > request queuing)
>> >
>> > My Plan:
>> > I plan to migrate a classic ASP app to IIS 6 in hopes of using IIS 6's
>> > features above. My plan is to simply copy & paste my ASP pages into IIS
>> > 6
>> > and
>> > be done with it. However, I'm wondering if I need to migrate my code to
>> > ASP.NET in order to get the new IIS 6 features, or whether these
>> > features
>> > are
>> > enabled at the application pool regardless of code base.
>> >
>> > What are your thoughts?
>> >
>> > --
>> > Edgar
>>
>>
>> >> Stay informed about: Classic ASP & IIS 6 |
|
| Back to top |
|
| |
External
Since: Aug 25, 2006
Posts: 4
|
(Msg. 5) Posted: Tue Aug 29, 2006 7:01 am
Post subject: Re: Classic ASP & IIS 6 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Hi David, Thanks for the quick reply.
The ASP pages show this type of link:
http://localhost/display.asp?id=1258#
After the user clicks on the link, we call another Asp page that tracks the
link, username, and then receives the ID #, at which point, we replace the
URL location to point to package (exe/iso/etc).
I'll do more reading on: kernel mode response cache
--
Edgar
"David Wang [Msft]" wrote:
> Are the files downloaded via the ASP application, or as static resources
> served by IIS? In other words, are the downloads served as either:
> http://localhost/Application.asp?id=FileName.ext
> http://localhost/Downloads/FileName.ext
>
> I ask for this distinction because it directly affects necessary
> configuration and optimizations.
>
> On IIS6, you want to take advantage of the kernel mode response cache for
> the same chores because it will offer up to 10x performance improvement. It
> is not configured with those registry keys at all.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
>
> "mresanchez" <mresanchez DeleteThis @donot-spam.com> wrote in message
> news:5F81DD6C-8315-4408-8EF5-36CF5A3DF107@microsoft.com...
> > Hi David,
> >
> > In this particular case, the ASP application hosts files which users can
> > download.
> >
> > We host large files ranging from 50-700MB+ size. Some of the "largest"
> > and
> > "most" requested files, we cached in IIS 5 via this registry:
> >
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters
> >
> > "MaxCachedFileSize"=dword:3b9aca00 // So the server(s) is configured to
> > cache files that are up to 1000000000 bytes in size within the Inetinfo
> > process.
> > // The default
> > for MaxCachedFileSize is 256kb
> > "ObjectCacheTTL"=dword:ffffffff // The cache scavenger is
> > disabled...cached data will remain in memory until overwritten
> >
> > We're hoping IIS6/Win2k3 may help automate the "cache clean-up", and
> > IIS-application pool recycling. Right now, we do this manually whenever
> > the
> > site becomes unavailable.
> >
> > --
> > Edgar
> >
> >
> > "David Wang [Msft]" wrote:
> >
> >> IIS6's new features apply at the application pool level regardless of
> >> codebase. Thus, it applies to ASP, ASP.Net, PHP, Perl, JSP, etc.
> >>
> >> However, just because the feature applies does not mean it actually
> >> "works"
> >> with a given codebase. That depends on the codebase itself.
> >>
> >> I'd like to clarify the behavior of the IIS6 features you listed:
> >> - IIS6 does not detect memory leaks. It only detects amount of memory
> >> used
> >> by a process and recycles at a threshold
> >> - IIS6 does not do anything about access violations other than letting
> >> them
> >> happen and restarting a new w3wp.exe afterwards. If the AV happens too
> >> frequently, IIS will stop the Application Pool
> >> - Recycling Processes happen depending on health monitoring metrics
> >> - Managing Resources - Not certain what you are referencing
> >>
> >> Your ASP application should just work on IIS6. It may be able to take
> >> advantage of the new IIS6 features. It may be broken by the new IIS6
> >> features. You will have to describe the application and your settings in
> >> more detail to determine the actual answer.
> >>
> >> --
> >> //David
> >> IIS
> >> http://blogs.msdn.com/David.Wang
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> //
> >>
> >> "mresanchez" <mresanchez DeleteThis @donot-spam.com> wrote in message
> >> news:67FADCF2-2DF1-422E-B17B-4A8B58643416@microsoft.com...
> >> > I'm hoping you could help me out determining whether IIS 6's new
> >> > features
> >> > apply to Classic ASP or just .Net based apps.
> >> >
> >> > IIS 6's features I want for my Classic ASP app are:
> >> > detecting memory leaks,
> >> > access violations,
> >> > recycling processes,
> >> > managing resources (e.g. worker process isolation mode and kernel-level
> >> > request queuing)
> >> >
> >> > My Plan:
> >> > I plan to migrate a classic ASP app to IIS 6 in hopes of using IIS 6's
> >> > features above. My plan is to simply copy & paste my ASP pages into IIS
> >> > 6
> >> > and
> >> > be done with it. However, I'm wondering if I need to migrate my code to
> >> > ASP.NET in order to get the new IIS 6 features, or whether these
> >> > features
> >> > are
> >> > enabled at the application pool regardless of code base.
> >> >
> >> > What are your thoughts?
> >> >
> >> > --
> >> > Edgar
> >>
> >>
> >>
>
>
> >> Stay informed about: Classic ASP & IIS 6 |
|
| Back to top |
|
| |
External
Since: Aug 25, 2003
Posts: 2419
|
(Msg. 6) Posted: Tue Aug 29, 2006 3:56 pm
Post subject: Re: Classic ASP & IIS 6 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
http://blogs.msdn.com/david.wang/archive/2005/07/07/HOWTO_Use_Kernel_R...onse_Ca
Your URL suggests ASP sending the resource. It means that you cannot
leverage the Kernel mode Response Cache.
Are you sure the Registry key tweaks are working for you on IIS5? Because
they do not affect ASP sending the resource - so I do not think it comes
into effect at all.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"mresanchez" <mresanchez.DeleteThis@donot-spam.com> wrote in message
news:0131A78B-F17C-40C4-BE31-9343ABFDE928@microsoft.com...
> Hi David, Thanks for the quick reply.
>
> The ASP pages show this type of link:
>
> http://localhost/display.asp?id=1258#
>
> After the user clicks on the link, we call another Asp page that tracks
> the
> link, username, and then receives the ID #, at which point, we replace the
> URL location to point to package (exe/iso/etc).
>
> I'll do more reading on: kernel mode response cache
> --
> Edgar
>
>
> "David Wang [Msft]" wrote:
>
>> Are the files downloaded via the ASP application, or as static resources
>> served by IIS? In other words, are the downloads served as either:
>> http://localhost/Application.asp?id=FileName.ext
>> http://localhost/Downloads/FileName.ext
>>
>> I ask for this distinction because it directly affects necessary
>> configuration and optimizations.
>>
>> On IIS6, you want to take advantage of the kernel mode response cache for
>> the same chores because it will offer up to 10x performance improvement.
>> It
>> is not configured with those registry keys at all.
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> "mresanchez" <mresanchez.DeleteThis@donot-spam.com> wrote in message
>> news:5F81DD6C-8315-4408-8EF5-36CF5A3DF107@microsoft.com...
>> > Hi David,
>> >
>> > In this particular case, the ASP application hosts files which users
>> > can
>> > download.
>> >
>> > We host large files ranging from 50-700MB+ size. Some of the "largest"
>> > and
>> > "most" requested files, we cached in IIS 5 via this registry:
>> >
>> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters
>> >
>> > "MaxCachedFileSize"=dword:3b9aca00 // So the server(s) is configured
>> > to
>> > cache files that are up to 1000000000 bytes in size within the Inetinfo
>> > process.
>> > // The
>> > default
>> > for MaxCachedFileSize is 256kb
>> > "ObjectCacheTTL"=dword:ffffffff // The cache scavenger
>> > is
>> > disabled...cached data will remain in memory until overwritten
>> >
>> > We're hoping IIS6/Win2k3 may help automate the "cache clean-up", and
>> > IIS-application pool recycling. Right now, we do this manually
>> > whenever
>> > the
>> > site becomes unavailable.
>> >
>> > --
>> > Edgar
>> >
>> >
>> > "David Wang [Msft]" wrote:
>> >
>> >> IIS6's new features apply at the application pool level regardless of
>> >> codebase. Thus, it applies to ASP, ASP.Net, PHP, Perl, JSP, etc.
>> >>
>> >> However, just because the feature applies does not mean it actually
>> >> "works"
>> >> with a given codebase. That depends on the codebase itself.
>> >>
>> >> I'd like to clarify the behavior of the IIS6 features you listed:
>> >> - IIS6 does not detect memory leaks. It only detects amount of memory
>> >> used
>> >> by a process and recycles at a threshold
>> >> - IIS6 does not do anything about access violations other than letting
>> >> them
>> >> happen and restarting a new w3wp.exe afterwards. If the AV happens too
>> >> frequently, IIS will stop the Application Pool
>> >> - Recycling Processes happen depending on health monitoring metrics
>> >> - Managing Resources - Not certain what you are referencing
>> >>
>> >> Your ASP application should just work on IIS6. It may be able to take
>> >> advantage of the new IIS6 features. It may be broken by the new IIS6
>> >> features. You will have to describe the application and your settings
>> >> in
>> >> more detail to determine the actual answer.
>> >>
>> >> --
>> >> //David
>> >> IIS
>> >> http://blogs.msdn.com/David.Wang
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >> //
>> >>
>> >> "mresanchez" <mresanchez.DeleteThis@donot-spam.com> wrote in message
>> >> news:67FADCF2-2DF1-422E-B17B-4A8B58643416@microsoft.com...
>> >> > I'm hoping you could help me out determining whether IIS 6's new
>> >> > features
>> >> > apply to Classic ASP or just .Net based apps.
>> >> >
>> >> > IIS 6's features I want for my Classic ASP app are:
>> >> > detecting memory leaks,
>> >> > access violations,
>> >> > recycling processes,
>> >> > managing resources (e.g. worker process isolation mode and
>> >> > kernel-level
>> >> > request queuing)
>> >> >
>> >> > My Plan:
>> >> > I plan to migrate a classic ASP app to IIS 6 in hopes of using IIS
>> >> > 6's
>> >> > features above. My plan is to simply copy & paste my ASP pages into
>> >> > IIS
>> >> > 6
>> >> > and
>> >> > be done with it. However, I'm wondering if I need to migrate my code
>> >> > to
>> >> > ASP.NET in order to get the new IIS 6 features, or whether these
>> >> > features
>> >> > are
>> >> > enabled at the application pool regardless of code base.
>> >> >
>> >> > What are your thoughts?
>> >> >
>> >> > --
>> >> > Edgar
>> >>
>> >>
>> >>
>>
>>
>> >> Stay informed about: Classic ASP & IIS 6 |
|
| Back to top |
|
| |
External
Since: Aug 25, 2006
Posts: 4
|
(Msg. 7) Posted: Wed Aug 30, 2006 7:04 am
Post subject: Re: Classic ASP & IIS 6 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Hi David,
Yes. So far it has been 4 weeks and the registry keys seem to be helping.
At least, we haven't had to restart IIS5.0 in 3-4 weeks so far. May be
luck...
I'm double-checking on how the EXE/ISO/image is really called and downloaded
w/ one of the developers.
--
Edgar
"David Wang [Msft]" wrote:
> http://blogs.msdn.com/david.wang/archive/2005/07/07/HOWTO_Use_Kernel_R...onse_Ca
>
> Your URL suggests ASP sending the resource. It means that you cannot
> leverage the Kernel mode Response Cache.
>
> Are you sure the Registry key tweaks are working for you on IIS5? Because
> they do not affect ASP sending the resource - so I do not think it comes
> into effect at all.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
>
> "mresanchez" <mresanchez.DeleteThis@donot-spam.com> wrote in message
> news:0131A78B-F17C-40C4-BE31-9343ABFDE928@microsoft.com...
> > Hi David, Thanks for the quick reply.
> >
> > The ASP pages show this type of link:
> >
> > http://localhost/display.asp?id=1258#
> >
> > After the user clicks on the link, we call another Asp page that tracks
> > the
> > link, username, and then receives the ID #, at which point, we replace the
> > URL location to point to package (exe/iso/etc).
> >
> > I'll do more reading on: kernel mode response cache
> > --
> > Edgar
> >
> >
> > "David Wang [Msft]" wrote:
> >
> >> Are the files downloaded via the ASP application, or as static resources
> >> served by IIS? In other words, are the downloads served as either:
> >> http://localhost/Application.asp?id=FileName.ext
> >> http://localhost/Downloads/FileName.ext
> >>
> >> I ask for this distinction because it directly affects necessary
> >> configuration and optimizations.
> >>
> >> On IIS6, you want to take advantage of the kernel mode response cache for
> >> the same chores because it will offer up to 10x performance improvement.
> >> It
> >> is not configured with those registry keys at all.
> >>
> >> --
> >> //David
> >> IIS
> >> http://blogs.msdn.com/David.Wang
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> //
> >>
> >> "mresanchez" <mresanchez.DeleteThis@donot-spam.com> wrote in message
> >> news:5F81DD6C-8315-4408-8EF5-36CF5A3DF107@microsoft.com...
> >> > Hi David,
> >> >
> >> > In this particular case, the ASP application hosts files which users
> >> > can
> >> > download.
> >> >
> >> > We host large files ranging from 50-700MB+ size. Some of the "largest"
> >> > and
> >> > "most" requested files, we cached in IIS 5 via this registry:
> >> >
> >> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters
> >> >
> >> > "MaxCachedFileSize"=dword:3b9aca00 // So the server(s) is configured
> >> > to
> >> > cache files that are up to 1000000000 bytes in size within the Inetinfo
> >> > process.
> >> > // The
> >> > default
> >> > for MaxCachedFileSize is 256kb
> >> > "ObjectCacheTTL"=dword:ffffffff // The cache scavenger
> >> > is
> >> > disabled...cached data will remain in memory until overwritten
> >> >
> >> > We're hoping IIS6/Win2k3 may help automate the "cache clean-up", and
> >> > IIS-application pool recycling. Right now, we do this manually
> >> > whenever
> >> > the
> >> > site becomes unavailable.
> >> >
> >> > --
> >> > Edgar
> >> >
> >> >
> >> > "David Wang [Msft]" wrote:
> >> >
> >> >> IIS6's new features apply at the application pool level regardless of
> >> >> codebase. Thus, it applies to ASP, ASP.Net, PHP, Perl, JSP, etc.
> >> >>
> >> >> However, just because the feature applies does not mean it actually
> >> >> "works"
> >> >> with a given codebase. That depends on the codebase itself.
> >> >>
> >> >> I'd like to clarify the behavior of the IIS6 features you listed:
> >> >> - IIS6 does not detect memory leaks. It only detects amount of memory
> >> >> used
> >> >> by a process and recycles at a threshold
> >> >> - IIS6 does not do anything about access violations other than letting
> >> >> them
> >> >> happen and restarting a new w3wp.exe afterwards. If the AV happens too
> >> >> frequently, IIS will stop the Application Pool
> >> >> - Recycling Processes happen depending on health monitoring metrics
> >> >> - Managing Resources - Not certain what you are referencing
> >> >>
> >> >> Your ASP application should just work on IIS6. It may be able to take
> >> >> advantage of the new IIS6 features. It may be broken by the new IIS6
> >> >> features. You will have to describe the application and your settings
> >> >> in
> >> >> more detail to determine the actual answer.
> >> >>
> >> >> --
> >> >> //David
> >> >> IIS
> >> >> http://blogs.msdn.com/David.Wang
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >> //
> >> >>
> >> >> "mresanchez" <mresanchez.DeleteThis@donot-spam.com> wrote in message
> >> >> news:67FADCF2-2DF1-422E-B17B-4A8B58643416@microsoft.com...
> >> >> > I'm hoping you could help me out determining whether IIS 6's new
> >> >> > features
> >> >> > apply to Classic ASP or just .Net based apps.
> >> >> >
> >> >> > IIS 6's features I want for my Classic ASP app are:
> >> >> > detecting memory leaks,
> >> >> > access violations,
> >> >> > recycling processes,
> >> >> > managing resources (e.g. worker process isolation mode and
> >> >> > kernel-level
> >> >> > request queuing)
> >> >> >
> >> >> > My Plan:
> >> >> > I plan to migrate a classic ASP app to IIS 6 in hopes of using IIS
> >> >> > 6's
> >> >> > features above. My plan is to simply copy & paste my ASP pages into
> >> >> > IIS
> >> >> > 6
> >> >> > and
> >> >> > be done with it. However, I'm wondering if I need to migrate my code
> >> >> > to
> >> >> > ASP.NET in order to get the new IIS 6 features, or whether these
> >> >> > features
> >> >> > are
> >> >> > enabled at the application pool regardless of code base.
> >> >> >
> >> >> > What are your thoughts?
> >> >> >
> >> >> > --
> >> >> > Edgar
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
> >> Stay informed about: Classic ASP & IIS 6 |
|
| Back to top |
|
| |
|
FAQ
Search
Profile
Private Messages
Log in/Register/Password
