As is often the case, when you build a .Net web application performance all seems absolutely fine on your local machine.
Of course, you have unlimited resources and your probably not running a hundred websites. Even so you’ve probably written efficient code and done some general performance testing. Generally you’re pretty happy that you’ve written a reasonably performant application.
Then you deploy it to a Hosting company. You start seeing some strange results e.g. you intermittently have to re-login into your admin section; there are reports that the shopping cart is resetting itself etc.
What’s going on?
When looking through the Hosting companies packages one thing they fail to mention is that they will limit the amount of memory that your application can use.
Don’t get me wrong, you can’t allow one application to use all the server resources but some of the allowances are just a joke – 128mb in this day age won’t run anything!
Below is a non-scientific survey of a few suppliers picked at random – apart from ASPNetHosting who I was having the problem with. DiscountASP are a company that I use for other applications and never had a problem with. Even in this small sample it is amazing to see the wide variety in allowances.
Tips:
- Try and go with the latest technology on offer as memory can be much cheaper.
- Make sure you upgrade where your host allows you to do so.
- For example the following is a quote from DiscountASP: “100 MB of memory on IIS 6, 200 MB of memory on IIS 7, and 300 MB of memory on IIS 8”. The have an option in their control panel where you can automatically upgrade for free!
No comments:
Post a Comment