The real goal in load testing is to prove that the application and hardware are able to handle a target load that the business finds acceptable and still returns pages within a reasonable time. If you are intending to change functionality on the site, you can do a baseline loadtest and compare the performance after any changes to the site. Do you need to make sure the website is able to handle spike loads on a single page or two of X requests per second?Īre you intending on increasing the customers of the site, in which case take the current IIS log load and forumlate webtests that can simulate that range of page requests, but load for the expected concurrent users. Next step is to formulate a goal or two for the testing. Querying that will give you an idea of peak load. The free Webstress Tool is a load test tool that enables you to test how your web servers respond to normal and excessive loads. Log Parser 2 is the tool I would use should get the IIS logs into a database. The first step you should take is to look at your IIS logs to find out what is going on there. You can record a browsing session as a single test and it will allow you to read the perfmon stats from both your webserver and database easily enough. With Pingdom you can monitor your websites uptime, performance, and interactions for a better end-user-experience. We use more than 70 global polling locations to test and verify our customers websites 24/7, all year long. I found Visual Studio Test edition easier to test with (though it is not free). Pingdom offers cost-effective and reliable uptime and performance monitoring for your website. I imagine I'd want to monitor both the web server and the database server for testing load however when setting up scenarios to load test the web server I'd have to use pages that query the database to see any load on the database server at the same time.Īre web servers and database servers generally tested simultaneously or are they done as separate tests?Īs you can see I'm pretty clueless as to the whole operation so any incite as to how to go about this would be very helpful.įYI I have been tinkering with Pylot and was able to create and run a scenario against our site but I'm not sure what I should be looking for in the results or if the scenario I created is even a scenario worth measuring for our site. Our web site is on a multi-tier system complete with a separate database server (IIS 7 Web Server, SQL Server 2000 db). Every search I make on google for "how to load test a web site" just comes back with various companies and software to physically do the load testing.įor now I'm more interested in how to actually go about setting up a load test like what I should take into account prior to load testing, what pages within my site I should be testing load against and what things I'm going to want to monitor when doing the test. I've been tasked with stress/load testing our company web site out of the blue and know nothing about doing so.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |