The story behind this is how to test the hosting performance of the largest WordPress host on the web. In order to determine how our trusteeship is measured, we started with simple internal practices and soon became a fascinating journey of self discovery. Decide on a trip to share with blog readers. Ultimately, we are proud of our integrity and honesty in these areas. And once we decide to ride you to go, – one of the main goals is (* * * in addition to kicking) to be completely open and transparent. Both the published results and our test methods are. We can rely on this, everything is legal, and nothing will waver in our favor. The
This is what you can get from this article. Internally understand how one of the company’s internal experts conducts wpmu dev hosting tests on the most popular platform in the business. Please follow suit and freely reproduce our methodology* BTW, all the tools mentioned in this article are completely free! What happened to everything? Male dev man cut off his own work in this host battle. The first step is to create an account on the hosting provider we want to deal with wpmu dev. In other words, in this comparison, the courageous hosting providers of dev combat include: The
The de WPE engine flywheel virtual machine gateway site ground KinStar blue hosts we selected these 9 hosts. Because these two platforms are not only one of the largest names in WP hosting, but also the platforms that members pass on word of mouth in dialogues and questionnaires. We also know that no matter who we choose to compare wpmu dev with, we cannot please everyone. Therefore, if you have any suggestions to compare with dev in the future, please let me know, and I will try my best to incorporate them into the next round of testing. Go ahead… We compared the basic plans of various hosting providers to maximize fairness in testing. The
We also use the same default test site to add it to each hosting plan. The following is the test website we use (dog lovers prepare \
We also want to test the speed of each host, because it is important to provide timely service to customers. Therefore, we ran two basic performance tests on each host. Managed load test. Speed (ttfb) test. Starting with the managed load test, how do the two tests unfold: Test the number of concurrent users that each managed server can handle. For load testing, we provide a free load testing service that can stress test web applications and APIs through thousands of simultaneous connections. \
Male loader IO is where you visit if you want to know what the host actually consists of. Loader IO allows you to run three different types of tests. 1. \
The goal is to test how each managed server responds to user pressure.
We decided to run the \
All tests were run for 5 minutes, and the error failure was set to 1% from the time the error occurred. These errors include timeout, 400\/500, and network errors (all cumulative 1%). The test stops immediately and selects 1% as the lowest possible value to provide the most accurate interpretation value for the largest parallel client. For example, if the failure setting is 50%, the number of parallel clients will be much higher, but more users are allowed, so it is important (due to the higher error setting). In fact, they receive an error response, so they cannot calculate. In other words, visitors are essentially lost. The
Measurements we consider. In this particular test, we focus on the \
For example, suppose the maximum number of parallel clients is 50. This means that at least 50 people can access the site before the server crashes. Therefore, if 60 people try to access it at the same time, the server will restart, restart and run, and the internal server error will be displayed in the next few minutes. That is, you will lose your visitors. Here is a good metaphor to use. \
By default, if there are fewer parallel client functions, the risk of server failure and loss of visitors is higher. Therefore, it is recommended that the host have a higher parallel client number (even if the response time is slightly slow). Next, test the speed of each host. To test the speed, we used the performance test tool of keycdn. In short, the tool tests and measures the performance of all URLs in 10 different locations around the world. The content of the test itself is not much. Just paste the URL you want to test and press the button. In addition, it is free and can be used for your own tests. The performance test tool of keycdn provides a simple method to test the ttfb of each host. The retrieved results provide analysis of load time and HTTP response headers. Below: This is an excellent analysis of the host speed and performance at different locations. From the table above, we can see that the most concerned indicator in this test is \
In some cases, reading ttfb in Amsterdam is always better. Therefore, we decided to provide ttfb interpretation values in two different ways to ensure fairness to all relevant hosts. \
