JMeter
JMeter charting, history and visualisation - JChav
Submitted by Antony Marcano on Fri, 17/11/2006 - 17:43. jMeter | performance testing[textile]"Julian Harty":http://www.testingreflections.com/blog/741 brought "JChav":http://jchav.blogspot.com/ to my attention today. It's an open source tool for generating charts from JMeter tests.
!http://www.cognitran.com/jchav/diggjchavresults/View%2BAll_thumb.png!:http://jchav.blogspot.com/
Or, as it is described on the JChav site:
Performance Metric Bling(You need to "know what a chav is":http://en.wikipedia.org/wiki/Chav for this to make sense)
Performance Tool Comparison: How LoadRunner,OpenSTA and JMeter stack up at runtime - 2
Submitted by Suresh Nageswaran on Mon, 28/02/2005 - 13:04. jMeter | Mercury LoadRunner | OpenSTA | performance testing[textile]
In _*The Republic*_, _Plato_ conjectured on the idea of the dual level reality. One of these is known as the divided line:
!http://oregonstate.edu/instruct/phl201/images/philosophers/plato/divided_line.gif!
Above the line are the attributes of objective reality; below the line are the attributes of relative reality. This is not very different from user experienced times and response times measured from engineered tests. The problem, then, is to know whether a tool, even a favourite one, tells an objective truth or a relative truth! :)
In _*The Republic*_, _Plato_ conjectured on the idea of the dual level reality. One of these is known as the divided line:
!http://oregonstate.edu/instruct/phl201/images/philosophers/plato/divided_line.gif!
Above the line are the attributes of objective reality; below the line are the attributes of relative reality. This is not very different from user experienced times and response times measured from engineered tests. The problem, then, is to know whether a tool, even a favourite one, tells an objective truth or a relative truth! :)
Performance Tool Comparison: How LoadRunner,OpenSTA and JMeter stack up at runtime -1
Submitted by Suresh Nageswaran on Mon, 28/02/2005 - 12:26. jMeter | Mercury LoadRunner | OpenSTA | performance testing[textile]
Comparing features among tools, especially performance testing tools, brings another dimension of complexity. The basic premise behind a performance test is to understand what response times can be expected by simulation of user traffic modeled along user actions. These response times may be TTLB (Time to Last Byte) measurements - and usually exclude browser render time. It is merely the time since the request was issued to the time the last byte of the response flowed into the network card on the machine. From the wire to a nicely formatted page on a browser is something not factored into the test.
Comparing features among tools, especially performance testing tools, brings another dimension of complexity. The basic premise behind a performance test is to understand what response times can be expected by simulation of user traffic modeled along user actions. These response times may be TTLB (Time to Last Byte) measurements - and usually exclude browser render time. It is merely the time since the request was issued to the time the last byte of the response flowed into the network card on the machine. From the wire to a nicely formatted page on a browser is something not factored into the test.