| Centralized Execution Scenario: | araguaia | ||
| Single sequence without splits. | |||
| The same activity, with the same data set is executed durint each task | |||
| Distributed Execution Scenario: | araguaia and iguacu | ||
| 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 | |||
| Distributed Execution Scenario: | araguaia, iguacu, anhumas and tigre | ||
| Cases execute in a single sequence of equal activities, without splits and joins. | |||
| The users are allocated at runtime in random order. Since each user (tasklist) is executing in a different host, the host of the next activity is choosed at runtime. | |||
| The activities are created in the user preferential host. | |||
| Hence, activities alternate between three machines: araguaia, iguacu and tigre. Consecutive activities may execute in the same host. | |||
| Case, process and role coordinators ececute in host araguaia | |||
| The TaskLists execute one in each host: araguaia, iguacu and tigre, each one representing one user. | |||
| All coordinators execute in host anhumas. | |||
| The test is started from host araguaia. | |||
| The same data set is read by all activities | |||
| Hosts: araguaia.pos.dcc.unicamp.br; iguacu.dcc.unicamp.br; anhumas.dcc.unicamp.br; tigre.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 | ||
| Host Name: | tigre | ||
| Manufacturer | Sun (Sun Microsystems) |
