Centralized Execution Scenario: | |||
Single sequence without splits. | |||
The same activity, with the same data set is executed durint each task | |||
Distributed Execution Scenario: | |||
Cases execute in a single sequence of equal activities, without splits and joins. | |||
Activities alternate between two machines: consecutive activities execute in different hosts. | |||
Case, process and role coordinators ececute in host araguaia | |||
The taskLists (2) execute in host iguacu. | |||
The test is started from host iguacu | |||
The same data set is read by all activities | |||
Hosts: araguaia.pos.dcc.unicamp.br and iguacu.dcc.unicamp.br | |||
Hosts Information: | |||
Host Name | araguaia | ||
Manufacturer | Sun (Sun Microsystems) | ||
System Model | Ultra 2 | ||
Main Memory | 380 MB | ||
Virtual Memory | 526 MB | ||
Host Name | iguacu | ||
Manufacturer | Sun (Sun Microsystems) | ||
System Model | Ultra 2 | ||
Main Memory | 252 MB | ||
Virtual Memory | 531 MB | ||
Timeout of the activities (minutes) | 5 | ||
Timeout of the coordinators (Case, Process and Role) (minutes) | 10 | ||
Timeout of the tasklist (minutes) | 5 | ||
Wait time between consecutive cases (seconds): | 20 | ||
Number of activities in the case: | 15 | ||
Number of users: | 2 | ||
Number of process coordinators: | 1 | ||
Wait time of the invoked application: | 20 | ||
Invoked application command line: | bubblesort 1000 | ||
Performs garbage collection at the end of the case? | no | ||
Total ammount of data exchanged between consecutive activities (KB): | 121 |