Standard_E64ds_v5 on Databricks
Standard_E64ds_v5 is a memory optimized Azure worker type with 64 vCPUs and 512 GB of memory. On Databricks it uses 22 DBUs an hour, so 1 node on Jobs Compute in East US costs $11.21 an hour: $6.60 for the DBUs and $4.61 to Azure for the machine.
Azure · Memory optimized · Edsv5
Standard_E64ds_v5 at a glance
- vCPUs
- 64
- Memory
- 512 GB
- Own SSD
- 2,400 GB
- DBUs an hour
- 22
- Classic compute
- With Photon
- 55
- DBUs an hour, Jobs Compute
- 1 node an hour
- $11.21
- Jobs Compute, East US
1 node an hour on each kind of compute
In East US on the Premium plan. Databricks charges the DBUs, Azure the machine. A cluster pays this for every worker and for the driver.
| Compute | DBUs an hour | A DBU | Databricks | Machine | An hour |
|---|---|---|---|---|---|
| Jobs Compute | 22 | $0.30 | $6.60 | $4.61 | $11.21 |
| Jobs Compute + Photon | 55 | $0.30 | $16.50 | $4.61 | $21.11 |
| All-Purpose Compute | 22 | $0.55 | $12.10 | $4.61 | $16.71 |
| All-Purpose Compute + Photon | 44 | $0.55 | $24.20 | $4.61 | $28.81 |
| Lakeflow pipelines Core | 22 | $0.30 | $6.60 | $4.61 | $11.21 |
| Lakeflow pipelines Pro | 22 | $0.38 | $8.36 | $4.61 | $12.97 |
| Lakeflow pipelines Advanced | 22 | $0.54 | $11.88 | $4.61 | $16.49 |
In each region
1 node an hour on Jobs Compute, Premium, cheapest first.
| Region | Machine | An hour |
|---|---|---|
| East US | $4.61 | $11.21 |
| East US 2 | $4.61 | $11.21 |
| West US 2 | $4.61 | $11.21 |
| West US 3 | $4.61 | $11.21 |
| Central India | $4.83 | $11.43 |
| Sweden Central | $4.86 | $11.46 |
| Canada Central | $5.06 | $11.66 |
| North Europe | $5.12 | $11.72 |
| Central US | $5.21 | $11.81 |
| UK South | $5.41 | $12.01 |
| France Central | $5.41 | $12.01 |
| West Europe | $5.54 | $12.14 |
| Germany West Central | $5.54 | $12.14 |
| Southeast Asia | $5.57 | $12.17 |
| Japan East | $5.57 | $12.17 |
| Australia East | $5.57 | $12.17 |
| Brazil South | $7.30 | $13.90 |
Other memory optimized sizes
- Standard_E4ds_v54 vCPUs, 32 GB, 1.5 DBUs an hour
- Standard_E8ds_v58 vCPUs, 64 GB, 2.75 DBUs an hour
- Standard_E16ds_v516 vCPUs, 128 GB, 5.5 DBUs an hour
- Standard_E32ds_v532 vCPUs, 256 GB, 11 DBUs an hour
- Standard_E48ds_v548 vCPUs, 384 GB, 16.5 DBUs an hour
- Standard_E64ds_v564 vCPUs, 512 GB, 22 DBUs an hour
- Standard_E96ds_v596 vCPUs, 672 GB, 33 DBUs an hour
Questions
- How many DBUs does Standard_E64ds_v5 use on Databricks?
- Standard_E64ds_v5 uses 22 DBUs an hour on Databricks classic compute without Photon. With Photon it uses 55 DBUs an hour on Jobs Compute and 44 on All-Purpose Compute, as Databricks' price list gives them.
- How much does Standard_E64ds_v5 cost an hour on Databricks?
- In East US, 1 Standard_E64ds_v5 node on Jobs Compute costs $11.21 an hour: $6.60 to Databricks for 22 DBUs at $0.30 each, and $4.61 to Azure for the machine. On All-Purpose Compute the same node costs $16.71 an hour, and on Lakeflow pipelines Core $11.21. A cluster pays this for every worker and for the driver.
- Does Photon cost more on Standard_E64ds_v5?
- Yes, by the hour: with Photon, 1 Standard_E64ds_v5 node on Jobs Compute in East US costs $21.11 an hour instead of $11.21, because it uses 55 DBUs an hour instead of 22. It saves money only when the job finishes fast enough to make up the difference.
- Which region is cheapest for Standard_E64ds_v5 on Databricks?
- East US, at $11.21 an hour for 1 node on Jobs Compute, against $13.90 in Brazil South, the dearest of the 17 regions listed here that offer it. Databricks charges the same for a DBU of Jobs Compute in every Azure region listed, so the gap is the machine.
- What is the same size as Standard_E64ds_v5 on the other clouds?
- The nearest worker types of the same kind are r6id.16xlarge on AWS and n2-highmem-64 on Google Cloud. Each cloud gives its own DBUs an hour for its types, so compare what a cluster costs in the calculator, not the DBUs alone.
- What is the next size up or down from Standard_E64ds_v5?
- One size down is Standard_E48ds_v5, at 16.5 DBUs an hour; one size up is Standard_E96ds_v5, at 33. Within a family, DBUs and the machine price grow with the vCPUs, so 2 nodes of a size cost about what 1 node of twice the size costs.
Sources