Modify, add or delete HTTP request elements so that they reflect the pages that you wish to fetch with the request.Loop Count = Throughput * Time / Number of Threads. If you have a target time, and an approximate value for the throughput (the number of requests the server can handle in one second), you can calculate the Loop Count with this formula: Second-long tests may not yield relevant results, because the server may need some time to stabilize under the changed load conditions – new server threads need to be created, for example. If you wish to get a picture of how the server performs under constant load, aim for minute-long tests. This number will determine how many times each thread is run, and therefore controls the length of the test. In both thread groups, set the Loop Count.This is the number concurrent users you wish to simulate. In both thread groups, set the Number of Threads.Set host variable to the hostname of the server you wish to test.Activate the User Defined Variable element corresponding to your Drupal version deactivate the other. The following are the few customizations one needs to do before using it: The following figure shows how the plan document looks. This plan comes with HTTP request, header, and listener elements set up. While I was browsing for documentation on the topic, I found a sample JMeter plan specific for Drupal on Drupal Performance Testing Suite’s page. JMeter is a powerful open-source Java application with a wide variety of features, which makes it daunting to set up a test plan in it. Using JMeter, I tried to replicate the load the server was likely to undergo. The site had been in operation for quite some time, so we had existing statistics that helped us predict how many visitors the site would need to be able to serve. This post is a summary of the steps I took and my findings. As a web developer, I don't often have the opportunity to do load testing, so I had to do some research on the topic beforehand. In connection with the recent launch of a high-profile Drupal-based website, one of my responsibilities was to evaluate how well the then un-launched system would perform under the expected load.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |