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: utime2ymd ------------------------------------------------------------------------------ == High Throughput Example: 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 "<font color="blue">Simple Data Writer</font>" was used to produce much friendlier CSV results files. + 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. 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]] @@ -195, +195 @@ }}} === Overview of Several Output files === - 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 script `jtltotals.sh` (attachment:jtltotals.sh.txt -- 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. + 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` (attachment:jtltotals.sh.txt -- 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. {{{ jtl-file-totals.txt @@ -211, +211 @@ total,23040,,,,, }}} + === Conversion of JMeter timestamps === + The first field of a JTL output file is a Unix timestamp extended to milliseconds. The above script `jtltotals.sh` calls another script `utime2ymd` to convert start & end times into year-month-day.hour-min-sec (yyyymmdd.HHMMss). Usually the JTL timestamps are adjusted for your local timezone (eg. GMT plus or minus a few hours). The `utime2ymd` script uses the local timezone by default, but can also provide GMT values -- useful for converting x-thousand elapsed seconds into hhmmss. (attachment:utime2ymd.txt) Example of usage: + {{{ + $ utime2ymd 1158477785863 + 20060917.192305 local + + $ utime2ymd 3601 gmt + 19700101.010001 gmt + }}} + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
