Job script builder

Choose a queue, how much of it you want and for how long. The page writes a complete job script and says what the run costs. It only writes the script: you submit it yourself from an ECC login node with sbatch.

Loading the queues and the current rates…

The queue

Queue

Account (who is billed)

Job name

How much, and for how long

ask by cores ask by whole nodes

Cores

Hours

and minutes

How the machines are bought

on demand spot

On demand costs more and the machine is yours until the job ends. Spot costs much less, but Azure can take the machine back at any moment and the job is killed; use it only for work that can be restarted (#SBATCH --requeue) or that checkpoints.

The queue you picked

What it costs

Estimate	On demand	Spot

Credit

Your job script

Save it on ECC as mycase.sbatch

Before you submit

Availability is our node cap, not Azure's. Each queue may hand out only the number of nodes listed above; a job that asks for more waits, or is refused. Beyond that cap nothing is reserved for us: a machine is created when your job starts, which takes three to five minutes the first time.
Spot machines can be taken back with about 30 seconds' notice, at any point in the run. The price shown is today's spot price and it moves.
Copy your files first. azsync push on an ECC login node before you submit, azsync pull <folder> when the job has finished. The Azure machines cannot see ECC's file system.
These are list prices. They exclude storage and any agreement discount, and they change without notice.

No PHI, FERPA-protected, export-controlled or CUI data may be moved to Azure until the UKY security review of this service is complete. There are no backups and no snapshots on the Azure side: the copy that matters stays on ECC.

Center for Computational Sciences, University of Kentucky · current prices · Need help? Open a support ticket