Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-jmeter Wiki" for change notification.
The following page has been changed by robertpnz: http://wiki.apache.org/jakarta-jmeter/LogAnalysis The comment on the change is: links & copyedit ------------------------------------------------------------------------------ attachment:scripts_jmeter.zip - == High Throughput Example: Simple Data Writer, Bash scripts & Excel Graphs == + == Testing a High Volume Webservice: Simple Data Writer, Bash scripts & Excel Graphs == - For a telecomms project, JMeter was used to test a new high-availability integration layer, exposed to a few internal clients. Several instances of JMeter represented the different clients and varying load profiles. The default JMeter XML output is too verbose, and the files grew too enormous, so the '''Simple Data Writer''' was used to produce much friendlier CSV results files. + For a telecoms project, JMeter was used to test a new high-availability integration layer, exposed to a few internal clients (see also [:../UserManual/BuildWSTest:BuildWSTest]). Several instances of JMeter represented the different clients and varying load profiles. The default JMeter XML output is too verbose, and the files grew too enormous, so the '''Simple Data Writer''' was used to produce much friendlier CSV results files. I wanted to show throughput & response times in blocks of 1 minute; JMeter's inbuilt Graph function was not sufficient to process the volume of data. An example of the type of graph required follows. The reader will see that the JMeter test plan produced variations in load (normal, high & spike), and the response times were quite well-behaved. If the integration layer was performing poorly, the graph would show inconsistent throughput and fluctuating response times. [[BR]] attachment:throughput-graph.png [[BR]] === Simple Data Writer JTL files === - The Simple Data Writer conveys the same information as the default output, but the CSV format is much denser. Example: + JMeter's [http://jakarta.apache.org/jmeter/usermanual/build-monitor-test-plan.html Simple Data Writer] produces JTL output files which convey the same information as the default XML output, but the CSV format is much denser. Example: {{{ queryBalance.jtl @@ -197, +197 @@ === Overview of Several Output files === Script: attachment:jtltotals.sh.txt [[BR]] After a test run, all the JTL output files were gathered together (20 or so files) in a bunch of subdirectories. The analysis was conducted on a Windows PC with MinGW/MinSYS and a few other tools (msys-dtk, gnu bc, gnu paste, gVim). For an overview of total vs. projected throughput, I used the shell script `jtltotals.sh` (a bit kludgy but hey I'm a tester not a developer!). It collates [total throughput, start time, end time, time elapsed, average response time] for each output file. - This script will produce a file 'jtl-file-totals.txt'. A sample of output is shown below. + This script will produce a (comma-delimited) file 'jtl-file-totals.txt'. A sample of output is shown below. {{{ jtl-file-totals.txt @@ -253, +253 @@ } }}} - An example session, using `jtlmin.sh` to process a JTL file. The file produced, `queryBalance.jtl.OUT`, can now be used to produce throughput graph. Response times can also be included on the secondary axis, as in the diagram above. These graphs were very good at showing when the integration layer was slow to respond and when throughput varied from the original JMeter plan. + An example session, using `jtlmin.sh` to process a JTL file. The file produced, `queryBalance.jtl.OUT` (tab-delimited), can now be used to produce throughput graph. Response times can also be included on the secondary axis, as in the diagram above. These graphs were very good at showing when the integration layer was slow to respond and when throughput varied from the original JMeter plan. {{{ $ jtlmin.sh Usage: jtlmin.sh <filename> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
