stress-testing | 易学教程

ASP.NET Stress Testing

阅读更多关于 ASP.NET Stress Testing

问题 Is there a way to test an application where you simulate a hundred different clients connecting to a IIS server and asking the same data? At the customer where our project is running they have 400 computers and they often do stress tests with all computers. I on the other hand have only got my laptop... (and a development server). (In my case the data is asked through a WebORB Gateway). 回答1: ab is a tool that was designed for Apache, but you can use it with IIS. 回答2: HP (formerly Mercury)

Best way to stress test a website [duplicate]

阅读更多关于 Best way to stress test a website [duplicate]

This question already has an answer here: ASP.NET Stress Testing 6 answers This may be the wrong question to ask but, what's the best way to replicate a large load on an asp.net web application? Is there an easy way to simulate many requests on particular pages? Or is the best thing to use a profiler to track a single request and then work out from that if the performance is ok? It would be good to know how well a web app works with a server spec. I'd like to be able to simulate heavy traffic on my testing server so that I can work out if the production server is good enough (specifically with

JMeter and JavaScript

阅读更多关于 JMeter and JavaScript

问题 When I make HTTP Request in JMeter I get Response data like "This page uses JavaScript and requires a JavaScript enabled browser." How is it possible to fix this problem. 回答1: JMeter is not a browser, and does not interpret the JavaScript in downloaded pages. From the JMeter wiki: JMeter does not process Javascript or applets embedded in HTML pages. JMeter can download the relevant resources (some embedded resources are downloaded automatically if the correct options are set), but it does not

Performing a Stress Test on Web Application?

阅读更多关于 Performing a Stress Test on Web Application?

In the past, I used Microsoft Web Application Stress Tool and Pylot to stress test web applications. I'd written a simple home page, login script, and site walkthrough (in an ecommerce site adding a few items to a cart and checkout). Just hitting the homepage hard with a handful of developers would almost always locate a major problem. More scalability problems would surface at the second stage, and even more - after the launch. The URL of the tools I used were Microsoft Homer (aka Microsoft Web Application Stress Tool ) and Pylot . The reports generated by these tools never made much sense to