0.2.37
Upgrade to the latest CLI:
QueueDepthAutoscaler
Added to V2You can control your autoscaling behavior with QueueDepthAutoscaler
.
QueueDepthAutoscaler
takes two parameters:
max_containers
tasks_per_container
In addition, for those using vertical scaling (multiple workers on the same container), concurrency
has been renamed to workers
(following the conventions of V1).
You can now move files around Beam Volumes using the beam mv
CLI command:
This supports directories too:
beam login
Automatically add your API keys to your local machine with beam login
.
Your browser will open, and fire a callback that saves your Beam credentials to your local machine.
This eliminates the need to manually copy and paste your API keys from the dashboard into your shell.
You can install the CLI separately from the SDK using Homebrew:
We added a wrapper around PIL to make it easier to save PIL images as Outputs.
Output.from_pil_image(pil_image)
takes a PIL image and returns a pre-signed URL that points to the saved image.
0.2.37
Upgrade to the latest CLI:
QueueDepthAutoscaler
Added to V2You can control your autoscaling behavior with QueueDepthAutoscaler
.
QueueDepthAutoscaler
takes two parameters:
max_containers
tasks_per_container
In addition, for those using vertical scaling (multiple workers on the same container), concurrency
has been renamed to workers
(following the conventions of V1).
You can now move files around Beam Volumes using the beam mv
CLI command:
This supports directories too:
beam login
Automatically add your API keys to your local machine with beam login
.
Your browser will open, and fire a callback that saves your Beam credentials to your local machine.
This eliminates the need to manually copy and paste your API keys from the dashboard into your shell.
You can install the CLI separately from the SDK using Homebrew:
We added a wrapper around PIL to make it easier to save PIL images as Outputs.
Output.from_pil_image(pil_image)
takes a PIL image and returns a pre-signed URL that points to the saved image.