Skip to main content
A compute profile sets the compute resources behind your Explorer queries. Each profile has its own queue, so you can split workloads, such as a large profile for long, complex queries and a small one for quick ones. An organization can have 3 profiles by default.

​
Profile sizes

A larger profile runs complex queries faster and costs more per run.
Speed multipliers are approximate. Query time doesn’t scale linearly with size: moving from 1x to 2x won’t reliably turn a 30s query into a 15s one. Try a few sizes on your own workload to find the right one.

​
Manage profiles

Admins add, resize and delete profiles in Settings > Compute. A new profile takes a name and a size, and gets an identifier for use in the API.
Compute profiles with the Default profile at 16x
Add Compute Profile dialog with profile name and size
If your organization runs on a dedicated warehouse, Allium provisions and sizes its profiles. Contact your CSM to change them.

​
Run a query on a profile

Once your organization has two or more profiles, pick one in the query editor before you run. The query keeps that profile for later runs.
Compute profile picker set to Default 16x beside Run via API and Run
To pick a profile through the API, pass its identifier, not its name, to Execute Query. Admins can also list, create, resize and delete profiles with an admin’s API key.

​
Queues

Settings > Compute shows queued and running counts for each profile, and your recent query runs. Admins see every run in the organization. Cancel a queued or running query from its row, or reset a whole queue.