IIS UNC NAS

Hi David,

Thanks for the quick reply,
1.
The highest peak on any front end was 400 Network Commands (WMI Redirector)
But I will give it a try and using fewer MaxCmds.
What If I reach maxcmd on the front ends? What will happen?
I didn't observed any Work Item Shortages (WMI Server) and there are always
Available Work Items (WMI Server Work Queues)
How can I meassure if the NAS is overwhlemed?

2.
Maximum usage of memory pool nonpaged bytes on the NAS is 100 MB (no /3GB)
Is there a way to check the available WorkItems?

We are hosting static, ASP and ASP.NET (no custom ISAPI).
Especially the high traffic sites are ASP.NET.
How can I tune this?
Didn't found any special ASP.NET NAS UNC tuning tips.

Yes, performance tuning is the most ungraceful thing. You never know how
good your tweaks are ...
My only reliable measurement are my external agents for monitoring up/down
state of my websites.

best regards,
Jan




"David Wang" <w3.4you.RemoveThis@gmail.com> wrote in message
news:e9fc626e-b010-4161-9a4b-157389d703e2@c4g2000hsg.googlegroups.com...
1.
You have six front ends with:
"MaxCmds"=dword:00000464

But one back end with:
"MaxWorkItems"=dword:00002000

It is possible for your front ends to overwhelm the backend with more
outstanding MaxCmds than the NAS can simultaneously handle files for.

2.
Also, each WorkItem costs 20K non-paged pool memory. If NAS is 32bit,
size of non-paged pool memory depends on amount of RAM, up to max of
around 256MB. If the machine has /3GB, it halves the amount of non
paged pool memory available. So, depending on hardware characteristics
of your NAS, you may not have as many WorkItems as you think.

The above are some things that can result in what you observe.

Also, can you provide details of the application(s) running on the Web
Server? Because the tuning only focused on static files and ASP --
there are different things to tune for ASP.Net or any custom CGI and
ISAPI applications -- but as far as UNC throughput, they have to obey
the same constraint.

FYI: Performance tuning issues are really not going to show up in the
Event log. For a generic platform like IIS, you will need to provide
external agents to monitor what "acceptable performance" means to you
-- because IIS is just infrastructure so it tells you the values --
you have to determine if the values are good or bad.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Jan 10, 8:11 am, "Jan" <jd<remove>@immobilien.net> wrote:
> Hi,
>
> We have deployed a NAS (Windows 2003 Appliance) for our six front end
> windows webserver 2003 (32bit and 64bit) to serve as an image store.
>
> I have worked my way through
>
> http://technet2.microsoft.com/windowsserver/en/library/d73c798c-3ca3-...
>
> http://support.microsoft.com/kb/813776
>
> http://www.microsoft.com/technet/prodtechnol/windowsserver2003/techno...
>
> which were a great help.
>
> But every 2 to 3 hours under pressure all webserver are losing
> simultaneous
> thier connections to the NAS UNC Shares.
> There is no information in eventviewer or logfiles (NAS or WEB), only our
> monitoring software gives us the hint.
> Surfing to a website in this state producess a long wait till internet
> explorer starts rendering the startpage (especially images served from the
> NAS UNC share), thereafter everything seems fine for the next 2 to 3
> hours.
>
> Did I missed something?
> Is there any possibility to get a better performance from the NAS?
>
> Any hints or suggestions appreciated,
> Thanks in advance,
> Best Regards,
> Jan Dorninger
>
> Konfig for the WEBS:
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters]
> "DoDirMonitoringForUNC"=dword:00000000
> "FileAttributeCheckThreshold"=dword:0000012c
> "ObjectCacheTTL"=dword:0000012c
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP\Parameters]
> "EnableChangeNotificationForUNC"=dword:00000000
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\par­ameters]
> "MaxCmds"=dword:00000464
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> "MaxUserPort"=dword:0000fffe
> "TCPTimedWaitDelay"=dword:0000003c
>
> Konfig for the NAS:
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\paramete­rs]
> "MaxMpxCt"=dword:00000800
> "MaxWorkItems"=dword:00002000
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
> "NtfsDisable8dot3NameCreation"=dword:00000000
> "Win31FileSystem"=dword:00000000
> "Win95TruncatedExtensions"=dword:00000001
> "ContigFileAllocSize"=dword:00001000
> "NtfsDisableLastAccess"=dword:00000001
> "NtfsDisableLastAccessUpdate"=dword:00000001
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> "MaxUserPort"=dword:0000fffe
> "TCPTimedWaitDelay"=dword:0000003c
 >> Stay informed about: IIS UNC NAS 

I don't know of any UNC tuning tips for ASP.Net, but I know it is not
very friendly to UNC. IIS team talked with ASP.Net team and found that
ASP.Net is as unsophisticated as ASP on IIS 5 when it comes to UNC
(that is, it's not good at all -- for example, you turned off ASP's
file change notification with "EnableChangeNotificationForUNC"=dword:
00000000 but there is no equivalent for ASP.Net... so you can expect
the bad behavior from ASP.Net ).

My suspicion right now is that ASP.Net traffic with its file change
notification has enough combined MaxCmds on the front end to soak up
all the MaxWorkItems on your NAS, thus leaving the NAS unable to
respond to any more requests and things appear to "stall" for a while
until the prior workitems finish.

You probably want to surf around ASP.Net forums to see if ASP.Net has
gotten better with UNC -- because if it has not, then all your tuning
is moot point.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Jan 11, 12:59 am, "Jan" <jd<remove>@immobilien.net> wrote:
> Hi David,
>
> Thanks for the quick reply,
> 1.
> The highest peak on any front end was 400 Network Commands (WMI Redirector)
> But I will give it a try and using fewer MaxCmds.
> What If I reach maxcmd on the front ends? What will happen?
> I didn't observed any Work Item Shortages (WMI Server)  and there are always
> Available Work Items (WMI Server Work Queues)
> How can I meassure if the NAS is overwhlemed?
>
> 2.
> Maximum usage of memory pool nonpaged bytes on the NAS is 100 MB (no /3GB)
> Is there a way to check the available WorkItems?
>
> We are hosting static, ASP and ASP.NET (no custom ISAPI).
> Especially the high traffic sites are ASP.NET.
> How can I tune this?
> Didn't found any special ASP.NET NAS UNC tuning tips.
>
> Yes, performance tuning is the most ungraceful thing. You never know how
> good your tweaks are ...
> My only reliable measurement are my external agents for monitoring up/down
> state of my websites.
>
> best regards,
> Jan
>
> "David Wang" <w3.4... RemoveThis @gmail.com> wrote in message
>
> news:e9fc626e-b010-4161-9a4b-157389d703e2@c4g2000hsg.googlegroups.com...
> 1.
> You have six front ends with:
> "MaxCmds"=dword:00000464
>
> But one back end with:
> "MaxWorkItems"=dword:00002000
>
> It is possible for your front ends to overwhelm the backend with more
> outstanding MaxCmds than the NAS can simultaneously handle files for.
>
> 2.
> Also, each WorkItem costs 20K non-paged pool memory. If NAS is 32bit,
> size of non-paged pool memory depends on amount of RAM, up to max of
> around 256MB. If the machine has /3GB, it halves the amount of non
> paged pool memory available. So, depending on hardware characteristics
> of your NAS, you may not have as many WorkItems as you think.
>
> The above are some things that can result in what you observe.
>
> Also, can you provide details of the application(s) running on the Web
> Server? Because the tuning only focused on static files and ASP --
> there are different things to tune for ASP.Net or any custom CGI and
> ISAPI applications -- but as far as UNC throughput, they have to obey
> the same constraint.
>
> FYI: Performance tuning issues are really not going to show up in the
> Event log. For a generic platform like IIS, you will need to provide
> external agents to monitor what "acceptable performance" means to you
> -- because IIS is just infrastructure so it tells you the values --
> you have to determine if the values are good or bad.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Jan 10, 8:11 am, "Jan" <jd<remove>@immobilien.net> wrote:
>
>
>
> > Hi,
>
> > We have deployed a NAS (Windows 2003 Appliance) for our six front end
> > windows webserver 2003 (32bit and 64bit) to serve as an image store.
>
> > I have worked my way through
>
> >http://technet2.microsoft.com/windowsserver/en/library/d73c798c-3ca3-...
>
> >http://support.microsoft.com/kb/813776
>
> >http://www.microsoft.com/technet/prodtechnol/windowsserver2003/techno...
>
> > which were a great help.
>
> > But every 2 to 3 hours under pressure all webserver are losing
> > simultaneous
> > thier connections to the NAS UNC Shares.
> > There is no information in eventviewer or logfiles (NAS or WEB), only our
> > monitoring software gives us the hint.
> > Surfing to a website in this state producess a long wait till internet
> > explorer starts rendering the startpage (especially images served from the
> > NAS UNC share), thereafter everything seems fine for the next 2 to 3
> > hours.
>
> > Did I missed something?
> > Is there any possibility to get a better performance from the NAS?
>
> > Any hints or suggestions appreciated,
> > Thanks in advance,
> > Best Regards,
> > Jan Dorninger
>
> > Konfig for the WEBS:
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters]
> > "DoDirMonitoringForUNC"=dword:00000000
> > "FileAttributeCheckThreshold"=dword:0000012c
> > "ObjectCacheTTL"=dword:0000012c
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP\Parameters]
> > "EnableChangeNotificationForUNC"=dword:00000000
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\par­­ameters]
> > "MaxCmds"=dword:00000464
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> > "MaxUserPort"=dword:0000fffe
> > "TCPTimedWaitDelay"=dword:0000003c
>
> > Konfig for the NAS:
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\paramete­­rs]
> > "MaxMpxCt"=dword:00000800
> > "MaxWorkItems"=dword:00002000
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
> > "NtfsDisable8dot3NameCreation"=dword:00000000
> > "Win31FileSystem"=dword:00000000
> > "Win95TruncatedExtensions"=dword:00000001
> > "ContigFileAllocSize"=dword:00001000
> > "NtfsDisableLastAccess"=dword:00000001
> > "NtfsDisableLastAccessUpdate"=dword:00000001
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> > "MaxUserPort"=dword:0000fffe
> > "TCPTimedWaitDelay"=dword:0000003c- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: IIS UNC NAS 

I have only configured static jpg directories for UNC.
The ASP.NET code is local to the front end, only the big image store is on
the NAS (thousands of dirs and a lot more jpg/gif)

Did I miss a simple point like disableing ASP.NET on the UNC IIS Virtual
Directory (no Application, no ASP.NET config)?

I am going to look into ASP.NET tuning tips for UNC and will post my
results.



"David Wang" <w3.4you.DeleteThis@gmail.com> wrote in message
news:12a7adff-108a-4728-bc25-102fce550198@m34g2000hsf.googlegroups.com...
I don't know of any UNC tuning tips for ASP.Net, but I know it is not
very friendly to UNC. IIS team talked with ASP.Net team and found that
ASP.Net is as unsophisticated as ASP on IIS 5 when it comes to UNC
(that is, it's not good at all -- for example, you turned off ASP's
file change notification with "EnableChangeNotificationForUNC"=dword:
00000000 but there is no equivalent for ASP.Net... so you can expect
the bad behavior from ASP.Net ).

My suspicion right now is that ASP.Net traffic with its file change
notification has enough combined MaxCmds on the front end to soak up
all the MaxWorkItems on your NAS, thus leaving the NAS unable to
respond to any more requests and things appear to "stall" for a while
until the prior workitems finish.

You probably want to surf around ASP.Net forums to see if ASP.Net has
gotten better with UNC -- because if it has not, then all your tuning
is moot point.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Jan 11, 12:59 am, "Jan" <jd<remove>@immobilien.net> wrote:
> Hi David,
>
> Thanks for the quick reply,
> 1.
> The highest peak on any front end was 400 Network Commands (WMI
> Redirector)
> But I will give it a try and using fewer MaxCmds.
> What If I reach maxcmd on the front ends? What will happen?
> I didn't observed any Work Item Shortages (WMI Server) and there are
> always
> Available Work Items (WMI Server Work Queues)
> How can I meassure if the NAS is overwhlemed?
>
> 2.
> Maximum usage of memory pool nonpaged bytes on the NAS is 100 MB (no /3GB)
> Is there a way to check the available WorkItems?
>
> We are hosting static, ASP and ASP.NET (no custom ISAPI).
> Especially the high traffic sites are ASP.NET.
> How can I tune this?
> Didn't found any special ASP.NET NAS UNC tuning tips.
>
> Yes, performance tuning is the most ungraceful thing. You never know how
> good your tweaks are ...
> My only reliable measurement are my external agents for monitoring up/down
> state of my websites.
>
> best regards,
> Jan
>
> "David Wang" <w3.4....DeleteThis@gmail.com> wrote in message
>
> news:e9fc626e-b010-4161-9a4b-157389d703e2@c4g2000hsg.googlegroups.com...
> 1.
> You have six front ends with:
> "MaxCmds"=dword:00000464
>
> But one back end with:
> "MaxWorkItems"=dword:00002000
>
> It is possible for your front ends to overwhelm the backend with more
> outstanding MaxCmds than the NAS can simultaneously handle files for.
>
> 2.
> Also, each WorkItem costs 20K non-paged pool memory. If NAS is 32bit,
> size of non-paged pool memory depends on amount of RAM, up to max of
> around 256MB. If the machine has /3GB, it halves the amount of non
> paged pool memory available. So, depending on hardware characteristics
> of your NAS, you may not have as many WorkItems as you think.
>
> The above are some things that can result in what you observe.
>
> Also, can you provide details of the application(s) running on the Web
> Server? Because the tuning only focused on static files and ASP --
> there are different things to tune for ASP.Net or any custom CGI and
> ISAPI applications -- but as far as UNC throughput, they have to obey
> the same constraint.
>
> FYI: Performance tuning issues are really not going to show up in the
> Event log. For a generic platform like IIS, you will need to provide
> external agents to monitor what "acceptable performance" means to you
> -- because IIS is just infrastructure so it tells you the values --
> you have to determine if the values are good or bad.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Jan 10, 8:11 am, "Jan" <jd<remove>@immobilien.net> wrote:
>
>
>
> > Hi,
>
> > We have deployed a NAS (Windows 2003 Appliance) for our six front end
> > windows webserver 2003 (32bit and 64bit) to serve as an image store.
>
> > I have worked my way through
>
> >http://technet2.microsoft.com/windowsserver/en/library/d73c798c-3ca3-...
>
> >http://support.microsoft.com/kb/813776
>
> >http://www.microsoft.com/technet/prodtechnol/windowsserver2003/techno...
>
> > which were a great help.
>
> > But every 2 to 3 hours under pressure all webserver are losing
> > simultaneous
> > thier connections to the NAS UNC Shares.
> > There is no information in eventviewer or logfiles (NAS or WEB), only
> > our
> > monitoring software gives us the hint.
> > Surfing to a website in this state producess a long wait till internet
> > explorer starts rendering the startpage (especially images served from
> > the
> > NAS UNC share), thereafter everything seems fine for the next 2 to 3
> > hours.
>
> > Did I missed something?
> > Is there any possibility to get a better performance from the NAS?
>
> > Any hints or suggestions appreciated,
> > Thanks in advance,
> > Best Regards,
> > Jan Dorninger
>
> > Konfig for the WEBS:
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters]
> > "DoDirMonitoringForUNC"=dword:00000000
> > "FileAttributeCheckThreshold"=dword:0000012c
> > "ObjectCacheTTL"=dword:0000012c
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP\Parameters]
> > "EnableChangeNotificationForUNC"=dword:00000000
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\par­­ameters]
> > "MaxCmds"=dword:00000464
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> > "MaxUserPort"=dword:0000fffe
> > "TCPTimedWaitDelay"=dword:0000003c
>
> > Konfig for the NAS:
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\paramete­­rs]
> > "MaxMpxCt"=dword:00000800
> > "MaxWorkItems"=dword:00002000
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
> > "NtfsDisable8dot3NameCreation"=dword:00000000
> > "Win31FileSystem"=dword:00000000
> > "Win95TruncatedExtensions"=dword:00000001
> > "ContigFileAllocSize"=dword:00001000
> > "NtfsDisableLastAccess"=dword:00000001
> > "NtfsDisableLastAccessUpdate"=dword:00000001
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> > "MaxUserPort"=dword:0000fffe
> > "TCPTimedWaitDelay"=dword:0000003c- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: IIS UNC NAS