IIS
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
User Name:
Password:
Remember me
Go Back   Dev Shed ForumsSystem AdministrationIIS

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread Dev Shed Forums Sponsor:
  #1  
Old March 11th, 2006, 07:17 AM
arathra arathra is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Mar 2006
Posts: 38 arathra User rank is Sergeant (500 - 2000 Reputation Level)arathra User rank is Sergeant (500 - 2000 Reputation Level)arathra User rank is Sergeant (500 - 2000 Reputation Level)arathra User rank is Sergeant (500 - 2000 Reputation Level)arathra User rank is Sergeant (500 - 2000 Reputation Level) 
Time spent in forums: 6 h 34 m 38 sec
Reputation Power: 10
Process throttling

Hi,

I'm fairly new to IIS so any help appreciated!

Basically we have a server with about 30 of our own websites on it. Several of these use a lot of processing time when certain scripts on the sites are run and occasionally block the whole server. I end up having to log on and recyle the DefaultAppPool to reset the whole thing.

The scripts which are causing the problems are fairly low priority and we can afford to have them run slower and take longer.

I *think* I need to do something within IIS to set the processing time for the websites in question, but I'm not sure at all and don't know what the consequences will be.

So, I'd really appreciate it if someone could suggest a way of running these scripts without clogging up the whole server!

Many thanks!

Reply With Quote
  #2  
Old March 30th, 2006, 09:55 PM
webperf webperf is offline
Registered User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Mar 2006
Posts: 1 webperf User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 55 m
Reputation Power: 0
You could separate the sites running the scripts into their own app pool so that if they are taking long you can go and reccyle the apppools that the scripts are running in without affecting the rest of the server or the workloads running on the rest of the server.

Id keep an eye on the memory usage on the box to ensure that the new apppools arent going to cost you too much in terms of working set usage (base IIS process is about a 4MB working set then if you load php, asp, aspnet - you pay more). NOTE: however that IIS6 will idle out app pools that havent processed a request in a while so for app pools running sites that are infrequently used you dont pay anything in terms of RAM.

If you want to get really sophisticated (and your running the Enterprise Edition of WS2003) you can use the Windows System resource manager - check the support CD to identify the apppools that are running low prioirty stuff and literally have the OS steal processing cycles away from them based on a policy that you write.

Reply With Quote
Reply

Viewing: Dev Shed ForumsSystem AdministrationIIS > Process throttling


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump


Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 3 hosted by Hostway