2
|
1 |
This directory contains the juicer and two benchmark tests.
|
|
2 |
Taken together, these tests form the RMI reliability
|
|
3 |
suite. These three tests each function in two modes:
|
|
4 |
|
|
5 |
1) as short running JTREG regression tests
|
|
6 |
|
|
7 |
2) as long running RMI reliability tests
|
|
8 |
|
|
9 |
In addition, the two benchmark tests serves a third role:
|
|
10 |
|
|
11 |
3) as RMI and Serialization Performance tests run by
|
|
12 |
the Performance Group (http://perfwww.ireland/)
|
|
13 |
|
|
14 |
All of the ksh scripts under this directory are used
|
|
15 |
to run the RMI reliability suite and are not used
|
|
16 |
to run the JTREG regression tests. The one exception
|
|
17 |
to this is the scripts/create_benchmark_jars.ksh
|
|
18 |
script which creates the JAR files for the benchmarks
|
|
19 |
that are transfered to the Performance Group.
|
|
20 |
|
|
21 |
------------------------------------------------------
|
|
22 |
|
|
23 |
The remainder of this file describes how to run the
|
|
24 |
RMI reliability suite:
|
|
25 |
|
|
26 |
The launch_reliability.ksh script will build the
|
|
27 |
reliability suite, execute it, and clean up after itself.
|
|
28 |
It can be run from any directory with the proper
|
|
29 |
command line args.
|
|
30 |
|
|
31 |
For example, to run for 72 hours:
|
|
32 |
|
|
33 |
export SUITE_DIR=<path to this directory>
|
|
34 |
export JDK_DIR=<path to JDK being tested>
|
|
35 |
export RES_DIR=<path to results dir for this run>
|
|
36 |
export WORK_DIR=<path to temp working dir for this run>
|
|
37 |
export VMOPTS="-server -showversion"
|
|
38 |
|
|
39 |
rm -rf $RES_DIR $WORK_DIR
|
|
40 |
mkdir -p $RES_DIR $WORK_DIR
|
|
41 |
|
|
42 |
${SUITE_DIR}/launch_reliability.ksh \
|
|
43 |
$JDK_DIR \
|
|
44 |
$WORK_DIR \
|
|
45 |
$RES_DIR \
|
|
46 |
ksh \
|
|
47 |
$SUITE_DIR \
|
|
48 |
72 \
|
|
49 |
$VMOPTS >> $RES_DIR/launch_reliability.log 2>&1 &
|
|
50 |
|