Defining Cloud Resources#
When a workflow is executed and tasks are scheduled, the machines needed to run the task are provisioned automatically and managed for the user until task completion.
Tasks can be annotated with the resources they are expected to consume (eg. CPU, RAM, Storage, GPU) at runtime and these requests will be fullfilled during the scheduling process.
The number of cpu cores available to the task. If the task uses more than the alotted number of cores, the task can continue running but will be throttled.
The amount of memory available to the task. If the task uses more than the alotted amount of memory, the task will crash.
The amount of disc space available to the task. If the task uses more than the alotted amount of storage, the task will crash.
The number of GPUs available to the task.
Prespecified Task Resource#
The Latch SDK currently supports a set of prespecified task resource profiles represented as decorators:
small_task: 2 cpus, 4 gigs of memory, 100 GiB of storage, 0 gpus
medium_task: 30 cpus, 100 gigs of memory, 1500 GiB of storage, 0 gpus
large_task: 90 cpus, 170 gigs of memory, 4500 GiB of storage, 0 gpus
small_gpu_task: 7 cpus, 30 gigs of memory, 1500 GiB of storage, 1 gpu (24 gigs of VRAM, 9,216 cuda cores)
large_gpu_task: 31 cpus, 120 gigs of memory, 2000 GiB of storage, 1 gpu (24 gigs of VRAM, 9,216 cuda cores)
We use the tasks as follows:
from latch import small_task, large_gpu_task @small_task def my_task( ... ): ... @large_gpu_task def inference( ... ): ...
Custom Task Resource#
You can also specify task resources using
from latch import custom_task @custom_task(cpu=8, memory=64, storage_gib=1000) def my_task( ... ): ...