Audience Builder generates a workflow to unify
Attribute Tables, and
Because workflow tends to be a computationally heavy process, Treasure Data provides a way to avoid the compute resource conflicts with other jobs and processes you’re currently running. In Audience Builder, you can specify the type of Processing Engine to use and associated resource pools.
You can choose either
Presto and Hive or
Hive only as engine settings. Your selection determines which processing engine is used for the audience creation.
We generally recommend
Hive only, because it’s designed for large-scale joins and known for robustness, while “Presto and Hive” might perform faster for smaller data sets.
Resource Pool Setting
You can also specify which resource pools to use for each engine (Presto or Hive). Specifying resource pools gives you additional compute resource control.