21.01.2014 Views

Xiao Liu PhD Thesis.pdf - Faculty of Information and Communication ...

Xiao Liu PhD Thesis.pdf - Faculty of Information and Communication ...

Xiao Liu PhD Thesis.pdf - Faculty of Information and Communication ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

temporal consistency model, <strong>and</strong> hence to differentiate our strategy to the<br />

conventional TDA strategy, it is named PTDA. The pseudo-code for PTDA is<br />

presented in Figure 8.6.<br />

The actual process <strong>of</strong> PTDA is to borrow the expected time redundancy <strong>of</strong> the<br />

next workflow segment to compensate the current time deficit <strong>and</strong> then allocate the<br />

time deficit to the subsequent activities. The first task <strong>of</strong> PTDA is to calculate the<br />

expected time redundancy <strong>of</strong> the next workflow segment (Line 1). Normally, the<br />

next workflow segment is chosen as the workflow segment between the next activity<br />

<strong>of</strong> the checkpoint a p , i.e. a p+ 1 , <strong>and</strong> the end activity <strong>of</strong> the next local temporal<br />

constraint, say<br />

a p + m here. The expected time redundancy is defined as the<br />

difference between the temporal constraint <strong>and</strong> the execution time for the minimum<br />

acceptable temporal consistency state (Line 1). The expected time redundancy can<br />

be borrowed to compensate the time deficits for level I temporal violations. After<br />

that, the expected time redundancy is allocated to the subsequent activities within<br />

the workflow segment according to the proportion <strong>of</strong> their mean activity time<br />

redundancy as defined in [17] (Line 2 to Line 4). After that, re-assigned temporal<br />

constraints for each activity are returned (Line 5). Therefore, the actual<br />

compensation process for PTDA is to tighten the temporal constraints <strong>of</strong> the<br />

subsequent activities so as to ensure that the current scientific workflow execution is<br />

close to absolute consistency. However, since PTDA does not decrease the actual<br />

activity durations <strong>of</strong> the subsequent activities, it can h<strong>and</strong>le level I violations <strong>of</strong><br />

some local workflow segments but has no effectiveness on global constraints, e.g.<br />

the final deadline. To actually decrease the execution time <strong>of</strong> workflow segments<br />

(required by level II <strong>and</strong> level III temporal violations), more sophisticated h<strong>and</strong>ling<br />

strategies such as workflow rescheduling are required.<br />

ACOWR for Level Violations<br />

Since the pseudo-code for ACOWR is the integrated pseudo-code <strong>of</strong> the twostage<br />

local workflow rescheduling <strong>and</strong> ant colony optimisation strategy which are<br />

presented in Section 8.3.1 (Figure 8.1) <strong>and</strong> Section 8.3.3 (Figure 8.4) respectively, it<br />

is omitted here.<br />

140

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!