First of all, confirm whether the server hardware is enough to support the current traffic.
Ordinary P4 servers can generally support up to 100,000 independent IPs per day. If the number of visits is greater than this,
then you must first configure a higher-performance dedicated server to solve the problem
, otherwise no amount of optimization can completely solve the performance problem.
Secondly, optimize database access.
It is of course best to implement complete staticization of the front desk, as there is no need to access the database at all. However, for websites that are frequently updated,
staticization often cannot satisfy certain functions.
Caching technology is another solution, which is to store dynamic data in cache files. Dynamic web pages directly call
these files without having to access the database. Both WordPress and Z-Blog use this method extensively. Caching technology. I
also wrote a counter plug-in for Z-Blog, which is also based on this principle.
If it is indeed impossible to avoid access to the database, you can try to optimize the query SQL of the database. Avoid using statements such as
Select * from. Each query only returns the results you need, avoiding the need for a short period of time. A large number of
SQL queries.
Third, external hotlinking is prohibited.
Hotlinking of pictures or files from external websites often brings a lot of load pressure, so external hotlinking of pictures or files to one's own
should be strictly restricted. Fortunately, you can simply refer to it at present. To control hotlinking, Apache itself
can disable hotlinking through configuration. IIS also has some third-party ISAPIs that can achieve the same function.
Of course, forging referrals can also be done through code to achieve hotlinking, but currently there are not many people who deliberately forge referrals to hotlink.
You can ignore it or use non-technical means to solve it, such as on pictures. Add watermark.
Fourth, control the download of large files.
Downloading large files will take up a lot of traffic, and for non-SCSI hard drives, downloading a large number of files will consume
CPU, reducing the website's responsiveness. Therefore, try not to provide downloads of large files exceeding 2M. If
is required, it is recommended to place large files on another server.
Fifth, use different hosts to divert the main traffic
Place files on different hosts and provide different images for users to download. For example, if you feel that RSS files take up
a lot of traffic, then use services such as FeedBurner or FeedSky to place the RSS output on other hosts. In this way, most of the traffic pressure of other people's access will be concentrated on FeedBurner's host, and RSS will not be available. It takes up too many resources.
Sixth, use traffic analysis and statistics software.
Install a traffic analysis and statistics software on the website, you can instantly know which places consume a lot of traffic and which pages
need to be optimized. Therefore, accurate statistical analysis is required to solve the traffic problem. Can.