page225
311
Suspend Tasks
After testing, suspend tasks to prevent inadvertent execution.
ALTER TASK tsk_part_customer_order_asia SUSPEND;
ALTER TASK tsk_part_customer_order_europe SUSPEND;
ALTER TASK tsk_part_customer_order_africa SUSPEND;
ALTER TASK tsk_part_customer_order_america SUSPEND;
ALTER TASK tsk_part_customer_order_middle_east SUSPEND;
Load Testing
Load testing can be conducted in several ways assuming the raw or staging table has
been pre-populated.
•
Amend the External Parallelism Component developed in Chapter 6
to call the stored procedure five times, one call for each region.
•
Resume all five tasks.
•
Use an external orchestration tool.
Parallelizing data pipelines is dependent upon matching unused processing units in
a warehouse to the number of concurrent processes required to partition the underlying
table. You assume eight processing units; therefore, you should aim to split a single table
into eight segments. As you experienced with segmenting by region, there are only five
regions and hence five segments.
Assuming all parallel operations occur simultaneously, you expect to see both an
overall reduction in execution time and a higher concurrent use of a single warehouse.
Note the use of a task and stream may later be replaced by a single dynamic table
currently in public preview.
I suggest repeating the load test using a smaller warehouse size while checking for
both queueing and spills to disk to optimize cost and performance. The expectation is
that parallel processes will perform well with smaller warehouses.
I covered parallel testing in Chapter 6 and therefore leave testing for your further
investigation.
Chapter 8
parallelization