25.01.2015 Views

Cost-Based Optimization of Integration Flows - Datenbanken ...

Cost-Based Optimization of Integration Flows - Datenbanken ...

Cost-Based Optimization of Integration Flows - Datenbanken ...

SHOW MORE
SHOW LESS
  • No tags were found...

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

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

4 Vectorizing <strong>Integration</strong> <strong>Flows</strong><br />

(a) Latency WFPE<br />

(b) Execution Time WFPE<br />

(c) Latency VWFPE<br />

(d) Execution Time VWFPE<br />

(e) Latency CBVWFPE<br />

(f) Execution Time CBVWFPE<br />

Figure 4.22: Latency Time and Execution Time <strong>of</strong> Single Messages (for n = 250)<br />

most time-consuming operator. This waiting time at inter-bucket queues is included in the<br />

execution time <strong>of</strong> the whole plan. Note that the cost-based vectorized execution is faster<br />

than the full vectorization but with non-linear scaling because the number <strong>of</strong> execution<br />

buckets changed with increasing number <strong>of</strong> operators. Finally, the median <strong>of</strong> instancebased<br />

execution is close to the minimum, while for vectorized execution, it is close to the<br />

maximum. The substantiation is that there are only few messages (the first messages <strong>of</strong> a<br />

sequence) without any waiting time within inter-bucket queues when executing vectorized<br />

plans, while for all other messages, execution times include these waiting times.<br />

Deployment and Maintenance<br />

Furthermore, we evaluated the deployment and vectorization overhead with increasing<br />

number operators in a static manner (without dynamic plan rewriting).<br />

First, we measured the costs for the plan vectorization algorithm (A-PV) and the periodically<br />

invoked cost-based plan vectorization algorithm (A-CPV). Figure 4.23 shows those<br />

124

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

Saved successfully!

Ooh no, something went wrong!