AceCAST 5: what's new
AceCAST 5 is available now. Here is what changed: WRF 4.8, four physics updates and four new model outputs.
One published 2023 benchmark and two Azure list prices, worked line by line: what a GPU VM costs against one CPU VM and against sixteen, and what the sums leave out.

If you run WRF, the Weather Research and Forecasting model maintained by NCAR, someone will ask whether GPUs would make it cheaper. This article works the WRF GPU vs CPU cost question in the open. It uses one published benchmark and two public cloud list prices, and it shows every sum so that you can redo it with your own figures.
A note on scope: the benchmark measured AceCAST 2.1 and 3.0.1, both earlier releases.
The benchmark. On April 28, 2023, the NVIDIA Technical Blog published Microsoft and TempoQuest Accelerate Wind Energy Forecasts with AceCAST. The runs were made on Microsoft Azure. WRF ran on CPU virtual machines (VMs) of type Standard HB120rs_v3, each with 120 AMD EPYC Milan-X cores. AceCAST, which runs WRF on NVIDIA GPUs, ran on a Standard_ND96amsr_A100_v4 VM with 8 NVIDIA A100 GPUs. The article reports:
The prices. Azure list prices from the Azure Retail Prices API for the East US region, Linux, pay-as-you-go, on November 11, 2026:
The 2023 Azure study reported about 9× speed for AceCAST 2.1 against one CPU node, and similar performance to 18 CPU nodes; our cost example uses its separate AceCAST 3.0.1 comparison against 16 CPU nodes. One GPU node contained eight GPUs.
The cost of a run is the hourly price multiplied by the hours the run takes. Speed matters to cost because a faster run is billed for fewer hours.
| Comparison | CPU side | GPU side | Result |
|---|---|---|---|
| Hourly price, one VM each | $3.60 | $32.77 | 32.77 ÷ 3.60 = 9.10. The GPU VM costs about 9.1 times as much per hour. |
| Same forecast, one VM each, GPU at about 9 times the speed. Example: a job of 9 hours on the CPU VM. | 9 hours × $3.60 = $32.40 | 1 hour × $32.77 = $32.77 | 32.77 ÷ 32.40 = 1.011. The GPU run costs about 1% more, which is effectively the same, and the run takes about one ninth as long. |
| Similar speed, per hour: 18 CPU VMs against 1 GPU VM | 18 × $3.60 = $64.80 | $32.77 | (64.80 − 32.77) ÷ 64.80 = 0.494. The GPU side costs about 49% less. |
| Per hour: 16 CPU VMs against 1 GPU VM | 16 × $3.60 = $57.60 | $32.77 | (57.60 − 32.77) ÷ 57.60 = 0.431. The GPU side costs about 43% less per hour. |
| Same forecast, GPU at 1.07 times the speed: 16 CPU VMs against 1 GPU VM. Example: a job of 1 hour on the CPU VMs. | 1 hour × $57.60 = $57.60 | (1 ÷ 1.07) hours × $32.77 = $30.63 | (57.60 − 30.63) ÷ 57.60 = 0.468. 47% lower compute cost, before the AceCAST license. |
Two things stand out. With one VM on each side, the price ratio (about 9.1) and the speed ratio (about 9) cancel: you pay about the same and wait about one ninth as long. And by the benchmark's own numbers it took 18 CPU VMs, not 9, to match one GPU VM, so adding CPU VMs did not speed the run up in proportion. That is where the saving in the larger comparisons comes from.
The published speed is 1.07 times the CPU speed, so the GPU run takes 1 ÷ 1.07 = 0.934579 hours, displayed as 0.935 GPU node-hours. Costs use the unrounded value.
The authors reported 75% lower cost. Using the list rates shown here gives about 47% lower compute cost, before the AceCAST license. The original cost basis has not been reproduced here; a change in cloud prices alone does not explain the difference.
The 47% is a worked example, not a measurement: the 2023 speed ratios for AceCAST 2.1 and 3.0.1 multiplied by 2026 prices. Your own workload will have its own number.
The same article also reports that "AceCAST runs 16.8x faster than WRF for inner domain compute and communication times." That describes one part of a run, not the whole elapsed time you are billed for, so it is not used in the sums above.
Assumptions:
Left out:
The only number that settles the question is your own case, timed on both kinds of hardware.
Edit hourly rates and runs per month in the fixed benchmark example in the cost estimator, or request a trial and time your own case.

AceCAST 5 is available now. Here is what changed: WRF 4.8, four physics updates and four new model outputs.

Aerava runs a weather model around the site you pin and checks the result against your own storm, wind and turbine cut-out limits. Here is what you can run today, what it costs and what it says about accuracy.

A nowcast answers a narrow question: what will the storms do in the next few hours? Here is what the StormScope map shows, how Aerava's standing watch uses it for your saved sites, and where it stops.
Your forecast
Tell us the decision it has to serve. One short form reaches the team, and we review every request.