26.08.2013 Views

3.1 MB - Evernote

3.1 MB - Evernote

3.1 MB - Evernote

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Parallel Transaction-oriented Simulation<br />

LP1 just proceeds moving the Transactions in its Transaction chain according to their<br />

simulation time (Transaction priorities are ignored for this example). Apposed to that<br />

the rollback in aggressive cancellation would result in an anti-Transaction being sent out<br />

for x1 immediately which would cause a second rollback in LP2 and another anti-<br />

Transaction for x1’ being sent back to LP1. At the end both LPs will end up in the same<br />

state in which they were before x1 was moved by LP1. The same cycle of events would<br />

start again without any actual simulation progress.<br />

LP1<br />

LP2<br />

LP1<br />

LP2<br />

x1<br />

x1<br />

xy<br />

Lazy cancellation<br />

Aggressive cancellation<br />

xy-<br />

x1<br />

x1<br />

x2<br />

x1<br />

x2<br />

x1<br />

cycle 1<br />

Transaction transferred to other LP<br />

Anti-Transaction for other LP<br />

Rollback<br />

x1'<br />

x1'<br />

simulations. This has also been explored by the authors of [33]. They concluded that the<br />

37<br />

x1<br />

x1<br />

x1- x1'-<br />

x1<br />

x1'<br />

x1<br />

x1<br />

x2<br />

repeat of cycle 1<br />

time<br />

Figure 10: Cancellation in transaction-oriented simulation<br />

It can therefore be concluded that lazy cancellation needs to be used for a parallel<br />

transaction-oriented simulation based on an optimistic algorithm in order to avoid such<br />

endless loops.<br />

4.6 Load Balancing<br />

Load balancing and the automatic migration of slow LPs to nodes or processors that<br />

have a lighter work load has been suggested in order to reduce the runtime of parallel<br />

x2<br />

x1'<br />

...

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

Saved successfully!

Ooh no, something went wrong!