07-31-2020 08:05 AM - edited 07-23-2021 03:18 PM
When to use AMP Engine
Designer 2020.2 and Alteryx Analytics Hub introduce the new AMP Engine. It is most times faster than the e1 engine. This article will give some guidelines on how to decide which engine to use.
AMP stands for Alteryx Multi-threaded Processing. As implied by its name it enables processing of multiple packets in parallel. Contrasts this with e1 Engine that processes data record by record in sequence.
Prerequisites
Procedure
Experience shows that for modern multi core machines have best results. Adding additional cores can lead to almost linear performance increase.
Please note that the below are merely guidelines, however your mileage might vary.
Note also that not all tools have yet been converted to use AMP as AMP is actively being developed.
Testing AMP:
Run an existing workflow a few times in the e1 Engine, then run the workflow a few times with the AMP Engine. Compare the Results Pane (messages, warnings, errors, duration of the run) as well as any resulting data to check for differences.
To identify whether a workflow ran with the AMP Engine, check the results pan for a message stating "This is AMP; running [N] worker threads".
Best practices: