WONDER Execution Tests

 

I. Overhead Tests
II. Concurrent Cases Performance Tests
III. Data Exchange Performance Tests
IV. Processing Performance Tests
V. Hosts Information
 

Execution Tests

 


A set of performance tests were performed. In these tests, the system had a linear increase of the execution times with the increase of the number of concurrent cases and the volume of data exchanged. The overhead associated to Java objects creation represent almost 40\% of the total object migration time.

Back to Wonder Home Page


I. Overhead Tests

In these tests, the amount of data exchanged between activities is null. The wrapper application is not invoked. The main objective is to test the overhead of the activities migration and creation, without the interference of invoked applications and data transferred among hosts. One single case with 20 activities is executed in centralized and in a distributed scenarios.

Test 26 - Distributed X Centralized Execution of a case with 20 activities. No data is conveyed and no wrapper is invoked.

Back to Tests Menu


II. Concurrent Cases Performance Tests

In these tests, the amount of data exchanged between activities is fixed and equal to all activities. The wrapper application executes a sleep 20 UNIX shell command. The number of concurrent cases is the main variable in the tests. These tests were performed in Solaris hosts.


II.1. Single machine execution at host: araguaia.ics.uci.edu

Test 1 - 1 to 10 concurrent cases having 10 equal activities each. 10 Samples.

Test 2 - 1 to 20 concurrent cases having 20 equal activities each. 5 Samples.

Back to Tests Menu


II.2. Single machine execution at host: anhumas.ics.uci.edu

Test 7- 1 to 20 concurrent cases having 20 equal activities each. 5 Samples.

Back to Tests Menu


II.3. Distributed Execution (araguaia and iguacu)

Test 3 - Progressive execution of 1 to 10 concurrent cases. Each case was defined as a 10 equal activities sequence. The test was performed using 2 hosts having consecutive activities executing in different hosts. 10 Samples.

Test 4 - Progressive execution of 1 to 20 concurrent cases. Each case was defined as a 20 equal activities sequence. The test was performed using 2 hosts having consecutive activities executing in different hosts. 5 Samples.

Back to Tests Menu


II.4. Distributed  Execution (araguaia, iguacu, anhumas and tigre)

Test 22 - Progressive execution of 1 to 20 concurrent cases. Each case was defined as a 20-equal-activity sequence. The test was performed using 4 hosts. The host to execute the next activity is chosed, randomly, from the four hosts set, at runtime. 5 Samples.

Back to Tests Menu


II.5. Distributed X Centralized Execution (araguaia x araguaia and iguacu)

Test 5 - Progressive execution of 1 to 10 concurrent cases, execuiting in 2 machines, compared to Progresive execution of 1 to 10 centralized cases. Both tests use 10 equal activities for each case . 10 samples.

Test 6 - Progressive execution of 1 to 20 concurrent cases, executing in 2 machines, compared to Progressive execution of 1 to 20 centralized cases. Both tests use 20 equal activities for each case . 5 samples.

Back to Tests Menu


II.6. Distributed X Centralized Execution (araguaia x araguaia and iguacu x araguaia, iguacu, anhumas and tigre)

Test 25 - Progressive execution of 1 to 20 concurrent cases, execuiting in 2 and 4 machines, compared to Progresive execution of 1 to 20 centralized cases. Both tests use 20 equal activities for each case . The test was performed using 4 hosts. The host to execute the next activity is chosed, randomly, from the four hosts set, at runtime. 5 Samples.

Back to Tests Menu



III. Data Exchange Performance Tests

In these tests, the amount of data exchanged between activities is the main variable. The number of concurrent cases is fixed.

III.1. Single machine execution at host: araguaia.ics.uci.edu

Test 9 - Successive execution of a 20-activity case, with the data volume excanged between activities varing from 961KB to 14422KB. 5 samples.

III.2. Single machine execution at host: anhumas.ics.uci.edu

Test 10- Successive execution of a 20-activity case, with the data volume excanged between activities varing from 961KB to 14422KB. 5 samples.

Back to Tests Menu


III.3. Distributed Execution (araguaia and iguacu)

Test 11 - Sucessive execution of a 20-activity case, with the data volume excanged between activities varing from 961KB to 14422KB. The test was performed using 2 hosts having consecutive activities executing in different hosts. 5 Samples.

Back to Tests Menu


III.4. Distributed X Centralized Execution (araguaia x araguaia and iguacu)

Test 13 - Sucessive execution of a 20-activity case, with the data volume excanged between activities varing from 961KB to 14422KB. Centralized execution in a single host compared to the Distributed execution. Both tests use 20 equal activities in the case . 5 samples.

Back to Tests Menu



IV. Processing Performance Tests

In these tests, the amount of data exchanged between activities is fixed and equal to all activities. The wrapper application executes a bubble sort of 1000 random numbers. The number of concurrent cases is the main variable in the tests. These tests were performed in Solaris hosts.

The maximum number of concurrent cases that a centralized host could stand was 15, with 15 activities each.


IV.1. Single machine execution at host: araguaia.ics.uci.edu

Test 15 - 1 to 20 concurrent cases having 20 equal activities each. 5 Samples.

Test 17 - 1 to 20 concurrent cases having 15 equal activities each. 5 Samples.

Back to Tests Menu


IV.2. Single machine execution at host: anhumas.ics.uci.edu

Test 16 - 1 to 20 concurrent cases having 20 equal activities each. 5 Samples.

Test 18 - 1 to 20 concurrent cases having 15 equal activities each. 5 Samples.

Back to Tests Menu


IV.3. Distributed Execution (araguaia and iguacu)

Test 19 - Progressive execution of 1 to 20 concurrent cases. Each case was defined as a 15 equal activities sequence. The test was performed using 2 hosts having consecutive activities executing in different hosts. 5 Samples.

Back to Tests Menu


IV.4. Distributed Execution (araguaia, iguacu, anhumas and tigre)

Test 23 - Progressive execution of 1 to 20 concurrent cases. Each case was defined as a 15 equal activities sequence. The test was performed using 4 hosts. The host to execute the next activity is choosed, randomly, from the four hosts set, at runtime. 5 Samples.

Back to Tests Menu


IV.5. Distributed X Centralized Execution (araguaia x araguaia and iguacu)

Test 21- Progressive execution of 1 to 20 concurrent cases, executing in 2 machines, compared to Progresive execution of 1 to 20 centralized cases. Both tests use 15 equal activities for each case . 5 samples.

Back to Tests Menu


IV.6. Distributed X Centralized Execution (araguaia x araguaia and iguacu x araguaia, iguacu, anhumas and tigre)

Test 24- Progressive execution of 1 to 20 concurrent cases, execuiting in 2 and 4 machines, compared to Progresive execution of 1 to 20 centralized cases. The 3 tests use 15 equal activities for each case . 5 samples each.

Back to Tests Menu



V. Hosts Information

Host Name : araguaia
Host Aliases :
Host Address(es) : 143.106.7.14
Host ID : 8089b3de
Serial Number : 9024478
Manufacturer : Sun (Sun Microsystems)
System Model : Ultra 2
Main Memory : 380 MB
Virtual Memory : 526 MB
Host Name : iguacu
Host Aliases :
Host Address(es) : 143.106.7.2
Host ID : 8088edd4
Serial Number : 8973780
Manufacturer : Sun (Sun Microsystems)
System Model : Ultra 2
Main Memory : 252 MB
Virtual Memory : 531 MB
Host Name : tigre
Host Aliases :
Host Address(es) : 143.106.7.16
Host ID : 8081db37
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
Serial Number :
Manufacturer : Sun (Sun Microsystems)
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
System Model : Ultra Enterprise
Main Memory :
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
Virtual Memory :
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
ROM Version :
CPU Type : sparc
Number of CPUs : 2
App Architecture : sparc
Kernel Architecture : sun4u
OS Name : SunOS
OS Version : 5.7
Kernel Version : SunOS Release 5.7 
Version Generic_106541-08 [UNIX(R)
System V Release 4.0]
Host Name : anhumas
Host Aliases :
Host Address(es) : 143.106.7.92
Host ID : 80a75f7d
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
Serial Number :
Manufacturer : Sun (Sun Microsystems)
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
System Model : Ultra 4
Main Memory :
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
Virtual Memory :
sysinfo: /dev/ksyms is not a 32-bit kernel namelist
ROM Version :
CPU Type : sparc
Number of CPUs : 4
App Architecture : sparc
Kernel Architecture : sun4u
OS Name : SunOS
OS Version : 5.7
Kernel Version : SunOS Release 5.7
Version Generic_106541-08 [UNIX(R)
System V Release 4.0]

Back to Tests Menu


This page was last modified in April 6, 2000