6
Grid Performance with tkeden A Simple Walkthrough

Grid Performance with tkeden A Simple Walkthrough

Embed Size (px)

Citation preview

Grid Performance with tkeden

A Simple Walkthrough

2

The BrokerSequence:

A single task is loaded into the Broker.

After a certain time, set by the user (the Broker Speed), the task will move down to the Coordinator.

An amount of time (equal to the Broker Speed) will be added to the system’s timer (the Clock).

The Broker will show one less task.

Notes:

This process is repeated for each task fed into the Broker.

Coordinators are selected on a “least-loaded” basis.

3

The CoordinatorSequence:

A single task is loaded into the Coordinator.

After a certain time, set by the user (the Coord. Speed), the task will pass down to the Calculator.

An amount of time (equal to the Coord. Speed) will be added to the system’s timer (the Clock).

The Coordinator will show one less task.

Notes:

This process is repeated for each task fed into the Coordinator.

Calculators are selected on a “least-loaded” basis.

4

The CalculatorSequence:

A single task is loaded into the Calculator.

After a certain time, set by the user (the Calc. Speed), the task will be processed.

An amount of time (equal to the Calc. Speed) will be added to the system’s timer (the Clock).

The Calculator will show one less task.

An amount of time equal to that required to send the task back to the Broker via the Coordinator is also added to the system’s timer (the Clock). This amount equals two times the “Overhead” (as set by the user), plus the Broker and Coord. speeds.

Notes:

This process is repeated for each task fed to the Calculator.

5

Special Scenario 1: Deleting an Active Coordinator

Picture 1:

11 tasks are remaining in the Broker with 1 task in already assigned to each of the 3 Coordinators.

The user decides to remove one of the Coordinators by clicking on the “- Coord.” button in the toolbar,

Picture 2:

The last Coordinator to be added is removed.

The workload of this Coordinator is sent back up to the Broker, which now shows 12 tasks.

An overhead in time as set by the user, if any, is added to the system timer (the Clock).

6

Special Scenario 2: Deleting an Active Calculator

Picture 1:

There is 1 task in each of the 3 Coordinators.

There are 11 tasks and a single task in the 2 Calculators, respectively.

The user decides to delete a Calculator by pressing the “- Calc.” button on the toolbar.

Picture 2:

The last Calculator to be added is removed.

The workload of this Calculator is sent up to the last Coordinator to be added, which now shows 2 tasks.

An overhead in time as set by the user, if any, is added to the system timer (the Clock).