As the above statement, it will indeed lead to a large number of disk I/O operations (input, output) in reality. The consequences of large-scale I/O operations can be imagined, which will produce a large number of disk fragments and even cause bad channels to occur in hard disks.
So for generating statics, it is better to use text forums to better solve your needs. (The deputy W was born in a text forum. The name was ofstar at that time. Later, due to development difficulties, it was converted to MYSQL. The PW generated static pages, which is the pouting head that PW used to attract users' attention in the previous text method)
Of course, if you have a good memory, you should remember that when PW4, the PW forum could not access for a long time, and later it was restored to the data from a period of time ago. The official statement was that someone attacked and caused the hard disk to be damaged. In fact, this statement is relatively unreliable. Compared with the consequences of being attacked and caused by a large number of I/O operations, I personally prefer the latter.
Of course, if you pay more attention to 5d6d, you should know that one day a few days ago, 5d6d was inaccessible. According to unofficial news, it was because the hard disk was broken, and the reason for the damage was of course because a large number of users were doing I/O operations. Just imagine, in a forum, the disk I/O operations are only performed when the administrator updates the cache, and each member of 5d6d is an administrator. Imagine how big a test it is for the disk? So I am not surprised that the hard disk of 5d6d is broken.
Of course, many friends who are reading this article have used BT and have also heard that BT is very harmful to hard disks and cannot be opened too much. The so-called damage is the same thing as what we refer to here. A large amount of I/O causes disk fragmentation and even disk bad tracks.
Here are some practical examples to illustrate the problem.
3. About the Disadvantages of Pseudostatic
Of course, as the author of an article said, "If the traffic is slightly larger, the CPU will be overloaded when using pseudostatic. I will be able to hang up more than 300 people online at the same time, and when I do not use pseudostatic, there will be no hang up for more than 500 people online at the same time. My ISS number is 1000." This is true. Since pseudostatic is judged by regular judgment rather than real address, the responsibility for deciding which page is displayed is also determined by the direct assignment to the CPU. Therefore, the increase in CPU ownership is indeed the biggest disadvantage of pseudostatic.
4. How should we do it
Let's summarize.
1. There is no difference between using true static and false static.
2. Using true static may cause damage to the hard disk and affect the performance of the forum.
3. Using pseudo-static will occupy a certain amount of CPU share, and using it in large quantities will cause CPU overload.
4. The most important point is that we want to be static for SEO
so.
1. Using a truly static method can be directly eliminated, because no matter how it is generated, it will be very harmful to the hard disk.
2. Since the effect of authenticity and false static is the same, we can choose false static.
3. However, the large amount of pseudo-static use will cause CPU overload.
4. So we just need not use it in large quantities.
5. Since static is only for SEO to see, we only need to give SEO pseudo-static, and we don’t need to use it for users.
6. So we just need to use pseudostatic in Archiver specially provided for SEO crawling.
7. Thank you for your patience in reading the article I wrote.
8. If you have any questions or have different opinions, please feel free to express it.