There are various reasons for overloading IIS server due to simultaneous connections. You may encounter such issues due to DDoS attack on your site, poor coded site, and/or marketing campaigns that are directing traffic to your site.
If you have received a ticket from our help desk system explaining this situation, you will want to look in to the issue and resolve as soon as possible to bring your site back up and running. As we know distributed denial-of-service (DDoS) attack is one in which a multitude of compromised systems attack a single target, thereby causing denial of service for users of the targeted system. DDoS attack to your site can be easily resolved by using https://www.cloudflare.com/ service, which will help you to filter undesirable IP addresses.
If you suspect your site to have some glitches and vulnerabilities which may lead to simultaneous connections to your site, it is strongly recommended to recheck your site’s code, including database it uses (MySQL/MSSQL/MS Access etc.). Also you may try some optimization solutions for your site and databases.
If simultaneous connections was brought by extensive marketing campaigns, we would like to suggest checking out our VPS or VDC packages under our IX Web Hosting brand:
To continue preventing overloading the IIS server due to these kinds of issues, it is suggested to continue routine optimization to your sites. All though this can take time to do, you will be 100% sure in the long run your site will not lose its audience.
- Keeping your sites CMS and coding up-to-date
- Optimizing your sites databases regularly will help maintain site performance
- Please note that wide marketing campaigning may require more resources than shared hosting plan may offer, thus before you start actual campaign it is strongly recommended to recheck with our staff if your campaign may cause any high load on the IIS shared server you are located on.
Currently application pools on our servers are configured to use a limited reasonable amount of memory – in order to prevent server from being overloaded. Current settings for shared pools on servers:
ASP.NET v1.1 – 768MB
ASP.NET v2.0 – 768MB
ASP.NET v4.0 – 768MB
ASP – 768MB
Overload issue on shared application pool may occur due to different reasons. There are two most common reasons for shared pool overload. The first is the site which requires too much resources due to being poorly coded. Glitches in the site may lead to constant recycling of pool and as result to shared pool overload of IIS server.
The second will be due to server applications and sites with heavy traffic. If such traffic for you is expected we would like to suggest you considering one of our Cloud hosting plans, which will allow a growing site to work properly, without interruption. The benefits to moving to a dedicated environment will be the ability to better maintain the server resources available to you and ability to increase/decrease those resources per your discretion and needs.
You will want to implement actions to these issues so that they are resolved once and for all. It is not best practice to ignore application pool over usage. If you suspect your site to have some coding problems which may lead to recurring recycling of shared pool and as a consequence overload of it. You are able to settle this matter by rechecking initial code of your site and databases if your sites use one.
For demanding and lavish sites it is strongly recommended to use our VPS or VDC packages under our IX Web Hosting brand:
Such plans will allow sites to show their full potential. Same consideration can be applied for sites with big audience and sites that are used for advertising campaigns.
- Before deploying your site please be sure that your site is correctly configured and operates smoothly. Please also recheck that site’s database is working properly and will not cause misdoing of your site.
- If you suspect your site might require additional server resources, we kindly ask you to recheck with support if our shared hosting environment can suite your application.
- Before starting promotional campaign on your site, which you suspect may require additional server resources, please recheck with support if certain amount of visitors will not bring down your site.
Please keep in mind that MS Access databases are not designed for hosting environments, but for local one only. Using database of such kind can cause overload of IIS server in certain cases.
MS Access overload issues can be caused by a number of factors, including: size of the database, schema design, the complexity of the application, quality of the database, types of data, number of users, etc. Most often we find that MS Access cases were due to poor application design or pushing MS Access beyond its limitations.
Before starting using MS Access database, as you may already know, such database uses web server resources instead of database server
resources, which might increase load to web server.
One of the best ways to resolve issues that are related to IIS server overload due to MS Access is to convert your MS Access database into MSSQL database which will take a lot of time to complete, but please be sure that it will pay off in the end. It will increase performance of your site, make management of your database easier and certainly will eliminate additional load to web server.
The following guides should help you with accomplishing this task:
If converting your MS Access database to MSSQL is not a solution, you may be interested in other solutions as listed below:
In order to prevent IIS server overloads issues caused by extensive use of MS Access database you may follow these suggestions:
- Keep optimized your MS Access database. Make sure that it cooperates well and smoothly with your site and data which it is handling.
- You are able to convert your database to a web server friendly database management system e.g. MSSQL, Mysql etc.