Web site High-volume, highly concurrent processing

First, verify that the server hardware is sufficient to support current traffic.

Ordinary P4 server can generally support up to 100,000 independent IPs per day, if the traffic is larger than this, then you must first configure a more high-performance dedicated server to solve the problem, or how optimization can not completely solve the performance problem.

Second, optimize database access.

Server load is too large, an important reason is that the CPU load is too large, reduce the load on the server CPU, can effectively break the bottleneck. Using static pages can minimize the load on the CPU. Full static at the front desk, of course, the best, can not access the database at all, but for frequently updated sites, static often does not meet certain functions.

Caching technology

is another solution, is to store dynamic data in the cache file, dynamic Web pages directly call these files, and no longer access to the database, WordPress and Z-blog are heavily using this caching technology

If you do not avoid access to the database, you can try to optimize query SQL for the database. Avoid using statements such as Select *from, and each query returns only the results you need, avoiding a large number of SQL queries over a short period of time.

Third, prohibit the external hotlinking.

External Web site picture or file hotlinking often bring a lot of load pressure, so should strictly restrict the external to their own picture or file hotlinking, fortunately, can now simply through refer to control the hotlinking, Apache itself can be configured to prohibit hotlinking, IIS also has some third-party ISAPI that can implement the same functionality. Of course, forged refer can also be implemented by code to achieve hotlinking, but the current deliberate forgery refer hotlinking is not much, you can first not consider, or use non-technical means to solve, such as the image of the watermark added.

Four, control the download of large files.

Large file downloads can consume a lot of traffic, and for non-SCSI hard drives, a large number of file downloads can consume CPU, resulting in reduced responsiveness. Therefore, try not to provide more than 2M of large file download, if required to provide, it is recommended to put large files on another server. There are many free Web2.0 websites that offer image sharing and file sharing, so you can upload pictures and files to these sharing sites as much as possible.

V. Use different hosts to divert the main flow

Put the files on different hosts and provide different images for users to download. For example, if you feel that the RSS files occupy a large amount of traffic, then use services such as FeedBurner or Feedsky to put the RSS output on other hosts, so that others access to the traffic pressure is mostly concentrated on FeedBurner host, RSS does not occupy too much resources.

VI, use traffic analysis statistics software.

Install a traffic analysis and statistics software on the website to instantly know which places are consuming a lot of traffic and which pages need to be optimized, so it is necessary to have accurate statistical analysis to solve the traffic problems. I recommend using the Traffic analysis statistics software is googleanalytics (Google Analytics). I feel that the effect is very good in the process, I will explain in detail some of Googleanalytics's use of common sense and skills.

1. Sub-table

2. Read and write separation

3. Front-end optimization. Nginx Replacement Apache (front-end load balancer) personally think that the main or the distributed architecture is in place, MySQL and cache optimization is a limited optimization, and distributed architecture to make, PV growth, only need to heap machines can be expanded.

Learn to use explain statements to analyze SELECT statements, optimize the index, table structure, second, reasonable use of memcache and other caches, reduce the load of MySQL, and finally, if possible, try to use the Facebook hiphop-php to compile PHP, improve program efficiency.

Web site High-volume, highly concurrent processing