title: ASP.NET: How to reduce chance of getting error 503
body: <p>I have an asp.net app hosted at a (for now, unnamed) hosting company. This app uses a small MS SQL database.</p>
  
  <p>During the past couple of months, my complete website (whether it's the app page or plain static html page) was not accessible twice due to error 503. They just shut down the website without notifying me. However I monitor the website every few hours and called them when I found the problem. Then they restarted the application pool and everything worked again. </p>
  
  <p>They told me that my website/app reached their "Worker Process Limit" of "100MB" and that's the reason for their shutting it down.</p>
  
  <p>This seems to be the only hosting company that advertises their Worker Process Limit with their hosting plan so I don't have a basis of comparison with other companies's plans.</p>
  
  <p>So, my questions are:</p>
  
  <p>1.Could someone explain what the Worker Process Limit is in Windows server environment? And is 100MB considered small or adequate?</p>
  
  <p>2.How can I handle or avoid reaching this limit within my app? Is this possible or is it just the number of visitors is too high? I average only a few hundred visitors a day.</p>
  
  <p>Thanks.</p>