Performance testing-zee

Statement: here is just an introduction to the paralysis of the Olympic ticket booking website. There is no other commercial purpose. How to ensure performance in Performance TestingWe know that performance testing is for the entire architecture. The architecture includes two aspects: software and hardware. The hardware also includes many items, such as the motherboard, hard disk, memory, CPU, router, switch, and firewall. The software also includes many aspects, such as OS, application server, application, database, middleware, and etc. All these aspects should be taken into account for performance testing. In order to have a good grasp of the whole. Performance testing has the most substantial significance (from a technical perspective ). The paralysis of the Olympic ticket booking website is obviously caused by the submission of large amounts of data. We don't have to worry about its functional implementation. If the function cannot be implemented, it will certainly not be online. They certainly did performance tests before they went online. We do not need to doubt the effectiveness of their performance tests. The influence of the number of submitted users on the performance is not the result of a binary linear equation increasing. I think that negligence in any stage of this performance test may cause this result. First, the quality of performance testing engineers must be strictly required. Therefore, we must fully grasp these steps in the performance testing process. At the same time, another question was introduced: Who can grasp so many links? Even if you have more than a decade of experience, you cannot guarantee that you can grasp every detail in performance testing. Furthermore, human knowledge systems are limited. Therefore, when testing performance, we try to refine every problem. Then contact the relevant technical staff, even if the person performing the performance test has a good understanding of the network, database, and so on. We also try to bring everyone together to discuss performance issues. This can reduce the number of people who are easy to neglect. I often hear that some companies allow some people who do not have a long working experience to perform performance tests and some beginners to do so. These are nothing more than making a fake look for customers, indicating that our company has such a position. But what are their roles? How can this be reflected? How to measure? This is a very important issue. These should fall into the scope of Performance Testing Measurement. I feel very worthless for this kind of role. At the same time, I am also saddened by the attitude of some companies towards performance testing. If you want to do a good job in this position, you should find someone with the corresponding skills. It should not be used as a guise for customers. Of course, here we need to affirm some value that can not be ignored by performance testing engineers. Important performance tests were made for potential problems of some projects to avoid huge losses. I must emphasize that the technical depth of Performance Testing engineers plays a very important role in the performance testing results. Second, the importance of the team cannot be ignored. There is no doubt that we need to contact people to survive in society. In a project, we are also in contact with our colleagues. I think the team atmosphere can directly affect the efficiency and effect of my work. I don't think it is necessary to develop or test data in some companies. From the perspective of goal, a team has only one goal: to make the best products. However, the biggest problem with shirking responsibility lies in the unclear responsibilities of the job. This problem has caused many performance testers to feel like they have been playing around. Many other testers may also feel this way. This may be because the testing industry has developed rapidly in recent years. In fact, this is an industry that should never be impetuous. The technology industry should be steadfast and steady. Not as high and promising as some advertisements boast. Next, it is very important for the team to clearly define their responsibilities. Then there is the rationality of the plan. Many companies have serious problems with the plan. Sometimes it is because of insufficient project time, or insufficient workload judgment. Sometimes it is said that the tester needs to test the code written by the developer on the day. In this case, there is nothing to do during work hours, testers. After work, you always need to work overtime. This is just an unreasonable time. Other events with unreasonable resource arrangements are not described in detail. It is emphasized that the team has a good atmosphere, clear responsibilities, and reasonable resource arrangement. Third, the architecture of the software application system. This problem directly affects the performance of the entire system. If the system architecture is inherently poor, the system does not need to be tested. This point must be clearly described in the early stage. This problem is not solved by performance testers. However, performance testers must pay attention to this issue. A mature architecture should be considered. However, performance problems may also occur in the architecture. Pay attention to the performance test. Other technical factors are not listed one by one. The above describes performance tests from the technical perspective. Impact of other factors on Performance TestingFirst, user requirements. I think user requirements have a great impact on performance testing. This is because performance testing is intended for users. Sometimes the customer will ask how the process goes. Such a process may be the best for customers. There is no problem with the implementation of the function. However, the performance will be completely different. What should we consider most when all users flock? Do not paralyze the system. Rather than being slow. However, the process affects performance. If the performance requirements cannot be met according to the customer's requirements, do not hesitate to use other measures to balance performance issues. Performance testing engineers boldly put forward their own suggestions. Of course, sufficient arguments are required. Second, leaders. I think many times the decision-making by leaders in one sentence affects the final outcome. Similar to: Big leaders shoot their heads, middle leaders shoot their chests, and working ass. There is no way. I worked on a project outside, and the project leader was very rational. He asked me to perform a performance test. He will discuss with developers and tests to develop strategies. If performance problems occur, the responsibility is clearly divided. Change it immediately. However, the requirements of some leaders are indeed unreasonable. As a result, the following test cannot be performed. There is no way to do this. We can only make suggestions. Other external factors are not described here. In the morning, I was surprised to hear that the Olympic ticket booking website was paralyzed from a technical point of view. Is performance testing not well performed? Why does not I focus on performance testing? Or does it simulate the actual data volume of so many users? In my usual performance tests, if I perform a performance test on a module, how many users are there. I will fully analyze the effectiveness of the performance test. This allows you to analyze problems in depth when writing reports. If any part of the Olympic booking website is within the controllable range, such a problem may be a pure accident. I think it's not just an accident. Those who want to perform performance tests should not be taken away one by one.