J Meter Presentation 4
•Download as PPT, PDF•
0 likes•931 views
The document discusses performance testing in an agile environment. It outlines some pain points with traditional performance testing approaches and proposes performing performance testing earlier in the development cycle. It then provides an overview of JMeter, an open source performance testing tool, including what it is, who can use it, where and when it can be used, why it should be used, and how to use it. The document also briefly discusses distributed testing, integration with continuous integration tools, and alternatives to JMeter.
![Contents ,[object Object],[object Object],[object Object],[object Object],2/20/2010 First Draft](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to J Meter Presentation 4
Similar to J Meter Presentation 4 (20)
J Meter Presentation 4
- 3. What are the pain points ?
- 10. 2/20/2010 First Draft “ What cannot be measured, cannot be improved.”
- 11. Performance Testing
- 20. Distributed Testing
- 25. Questions 2/20/2010 First Draft
- 26. 2/20/2010 First Draft Sameer Naik - [email_address] Prasad Nirantar – [email_address] Contact Details
Editor's Notes
- Opening line here
- Explain what happens by
- Explain that this is agile
- //Get the definitions from the audience Now then, Its time for warm up before we proceed.
- //Get the definitions from the audience Now then, Its time for warm up before we proceed.
- Purposes 1) Demonstrate that the systems meets performance criteria. 2) Compare two systems to find which performs better. 3) Measure what parts of the system or workload cause the system to perform badly i.e. determine performance bottlenecks Performance testing can serve different purposes. In the diagnostic case, software engineers use tools such as profilers to measure what parts of a device or software contribute most to the poor performance or to establish throughput levels (and thresholds) for maintained acceptable response time. It is critical to the cost performance of a new system, that performance test efforts begin at the inception of the development project and extend through to deployment. The later a performance defect is detected, the higher the cost of remediation. This is true in the case of functional testing, but even more so with performance testing, due to the end-to-end nature of its scope.
- Performance testing technology employs one or more PCs or Unix servers to act as injectors – each emulating the presence of numbers of users and each running an automated sequence of interactions (recorded as a script, or as a series of scripts to emulate different types of user interaction) with the host whose performance is being tested. Usually, a separate PC acts as a test conductor, coordinating and gathering metrics from each of the injectors and collating performance data for reporting purposes. The usual sequence is to ramp up the load – starting with a small number of virtual users and increasing the number over a period to some maximum. The test result shows how the performance varies with the load, given as number of users vs response time. Various tools, are available to perform such tests. (Ref Wikipedia)
- Jmeter- mainly JMeter is a Java based Performance measuring tool. Open source Product by Apache History: Tomcat testing framework Lets have Jmeter in action
- Jmeter- mainly Hey wait a minute …there is a tool which does which you just described. What – Jmeter def, History Where – White box and Black box
- Running the
- Prasad to find the image including DB,LDAP, Application server ActiveMQ example http://activemq.apache.org/jmeter-performance-tests.html
- Performance Scalabitliy Reliability Not restricted to Agile but it can be used in more effectively Use of JMeter for monitoring performance of software subsystems, in a AGILE continuous iterative development situation Quick POC
- -Reports generated by the plugin
- //Get the definitions from the audience Now then, Its time for warm up before we proceed.
- Running the bad boy- Continuous Integration tool: Cruise Control