application| Performance | Virtual host we often find that when the number of visits to the site is constantly rising, it is a happy thing, but I also found that the increase in traffic also brought the burden of the server, especially for the virtual host users, Now the virtual host provider on the network mainly uses CPU upper limit control, when the server program (Web program) CPU occupancy exceeds a limit, the next visitors will be denied access, which is a thriving site is indeed a big blow, what can improve the overall performance?
First I should check, what our server program caused a serious waste of CPU resources, we found that waste generally occurs in the file or database operation of the general Small Web site are ASP + MDB (access), the disadvantage of access is when the open connection to a lot, Performance will drop, if the simultaneous database access to more than 30 performance will be significantly reduced, this time will also bring severe CPU resource loss
We recommend:
If your site's real-time update requirements are not particularly high, we recommend that you will be all access to the database page to rewrite the static page,--method is to use the FSO to write the file
If your updated data is not much, consider using application, such as total merchandise, current online numbers, so that you avoid frequent database access,
If you have a large number of data requirements to update the database, you can consider building the buffer itself, the specific operation is, build, application, first put your update data in the array, and then put the array in the application, when a data access conditions, you can use the counter ( More than how much data is updated) or the time (every over a period of time to take data) to achieve, the data will be read out to update the database
Because the operation of the application is in memory operation, so the loss of CPU time is very little, just occupy part of the memory space (so far, I have not heard which service provider on the use of memory restrictions, haha, opportunity ~ ~)
But also note that when the use of application is also insufficient, when reading or modifying application (put the data into the array) and manipulate the database, will produce errors, because the application can be locked is modified can not lock read, but this error is basically very small, You know, CPU's function is still very strong; the second is to use buffering only for some unimportant data, important data should directly manipulate the database, because when the server application, there is no, some service providers in order to improve server performance, in a day will restart IIS many times, In this case, you have to defend yourself, or deal with it in Application_End (this is good)
