3801234561
3801234562
3801234563
3801234564
3801234565
3801234566
3801234567
3801234568
:g/380/s//994
Thursday, February 11, 2010
Wednesday, February 10, 2010
JMeter Command Line Interface and Usage
Editing the default in the bin/JMeter.properties file
The following properties affect the summariser:
# Define the following property to automatically start a summariser
# with that name(applies to non-GUI mode ony)
summariser.name=summary
#
# interval between summaries (in seconds) default 3 minutes
summariser.interval=180
#
# Write messages to log file
summariser.log=true
#
# Write messages to System.out
summariser.out=true
[root@OCMPRBT2 bin]# ./jmeter -n -t /space/ukrain/voicemail/JmeterTest/myTest.jmx -l logOut.jtl &
summary + 108 in 21.8s = 5.0/s Avg: 1291 Min: 229 Max: 6317 Err: 0 (0.00%)
summary = 206 in 52.5s = 3.9/s Avg: 1827 Min: 229 Max: 6974 Err: 0 (0.00%)
The lines with "summary +" are incremental for the latest summariser period, the lines with "summary =" are cumulative. The above was with a summariser period of 20 secs, you can see the actual periods can sometimes be longer than the specified period and the length of the very first period is somewhat random. You get the throughput statistics as well as average, min and max response times, and how many errors were detected (assuming your JMeter test plan as assertions to detect errors).
The following properties affect the summariser:
# Define the following property to automatically start a summariser
# with that name(applies to non-GUI mode ony)
summariser.name=summary
#
# interval between summaries (in seconds) default 3 minutes
summariser.interval=180
#
# Write messages to log file
summariser.log=true
#
# Write messages to System.out
summariser.out=true
[root@OCMPRBT2 bin]# ./jmeter -n -t /space/ukrain/voicemail/JmeterTest/myTest.jmx -l logOut.jtl &
summary + 108 in 21.8s = 5.0/s Avg: 1291 Min: 229 Max: 6317 Err: 0 (0.00%)
summary = 206 in 52.5s = 3.9/s Avg: 1827 Min: 229 Max: 6974 Err: 0 (0.00%)
The lines with "summary +" are incremental for the latest summariser period, the lines with "summary =" are cumulative. The above was with a summariser period of 20 secs, you can see the actual periods can sometimes be longer than the specified period and the length of the very first period is somewhat random. You get the throughput statistics as well as average, min and max response times, and how many errors were detected (assuming your JMeter test plan as assertions to detect errors).
Tuesday, February 9, 2010
Built In Java Tools & JProfiler
List Java Processes
[serkans@serkanslnx smartconnect] jps -l
16563 sun.tools.jps.Jps
8765 ReporterGeneratePdf
Getting Thread Dump of a process with the given id
[root@serkanslnx telco]# jstack 1009
Attaching to process ID 1009, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 1.5.0_10-b03
Thread 1079: (state = IN_NATIVE)
- java.lang.UNIXProcess.waitForProcessExit(int) @bci=0 (Interpreted frame)
- java.lang.UNIXProcess.access$900(java.lang.UNIXProcess, int) @bci=2, line=20 (Interpreted frame)
- java.lang.UNIXProcess$1$1.run() @bci=165, line=132 (Interpreted frame)
JVM Arguments for Profiling and Debugging
-Xdebug -Xrunjdwp:transport=dt_socket,address=1980,server=y,suspend=n
OR
-Xdebug -Xrunjdwp:transport=dt_socket,address=1980,server=y,suspend=y
JVM_ARGS and LD_LIBRARY_PATH for JProfiler Debugging
-Xint -Xrunjprofiler:port=8849 -Xbootclasspath/a:/space/tools/jprofiler3/bin/agent.jar
and also
export LD_LIBRARY_PATH=/opt/jprofiler3/bin/linux-x86:$LD_LIBRARY_PATH
[serkans@serkanslnx smartconnect] jps -l
16563 sun.tools.jps.Jps
8765 ReporterGeneratePdf
Getting Thread Dump of a process with the given id
[root@serkanslnx telco]# jstack 1009
Attaching to process ID 1009, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 1.5.0_10-b03
Thread 1079: (state = IN_NATIVE)
- java.lang.UNIXProcess.waitForProcessExit(int) @bci=0 (Interpreted frame)
- java.lang.UNIXProcess.access$900(java.lang.UNIXProcess, int) @bci=2, line=20 (Interpreted frame)
- java.lang.UNIXProcess$1$1.run() @bci=165, line=132 (Interpreted frame)
JVM Arguments for Profiling and Debugging
-Xdebug -Xrunjdwp:transport=dt_socket,address=1980,server=y,suspend=n
OR
-Xdebug -Xrunjdwp:transport=dt_socket,address=1980,server=y,suspend=y
JVM_ARGS and LD_LIBRARY_PATH for JProfiler Debugging
-Xint -Xrunjprofiler:port=8849 -Xbootclasspath/a:/space/tools/jprofiler3/bin/agent.jar
and also
export LD_LIBRARY_PATH=/opt/jprofiler3/bin/linux-x86:$LD_LIBRARY_PATH
Monday, February 1, 2010
Adding Jars to your CLASSPATH in linux
export CLASSPATH=/space/mol.jar:$CLASSPATH
for j in $JMETER_HOME/lib/*.jar; do
CLASSPATH=$j:$CLASSPATH
echo $j
done
Note: This script initially adds the /space/mol.jar to the classpath.After than it adds all jars under the $JMETER_HOME/lib directory to the classpath.
for j in $JMETER_HOME/lib/*.jar; do
CLASSPATH=$j:$CLASSPATH
echo $j
done
Note: This script initially adds the /space/mol.jar to the classpath.After than it adds all jars under the $JMETER_HOME/lib directory to the classpath.
Reverse read from file in UNIX
Linux TAC Command
[root@x1 bin]# cat numbersInOrder.txt
1
2
3
4
5
6
7
8
9
10
[root@x1 bin]# tac numbersInOrders.txt
10
9
8
7
6
5
4
3
2
1
[root@x1 bin]#
[root@x1 bin]# cat numbersInOrder.txt
1
2
3
4
5
6
7
8
9
10
[root@x1 bin]# tac numbersInOrders.txt
10
9
8
7
6
5
4
3
2
1
[root@x1 bin]#
Subscribe to:
Posts (Atom)