More CPU and Memory for Tasks

CI/CD
Sep 24, 2024
Dan Manges
More CPU and Memory for Tasks

RWX now supports running tasks with more CPU and memory!

By default, RWX runs your tasks with 2 CPUs and 8 GB RAM, but you can customize this with the agent key on your task at the granularity of a single task in your run definition. That means you can use up to 64 CPUs and 256 GB RAM for CPU or memory intensive tasks and then run less intensive tasks on a smaller agent. It's one advantage among many of defining CI workflows as a directed acyclic graph (DAG).

While many CI platforms offer the ability to define jobs in a DAG, RWX is the only CI platform which defines steps in a DAG.

Supported Specifications

CPUsMemoryCost (per second)
28 GB$0.00014
416 GB$0.00028
832 GB$0.00056
1664 GB$0.00112
32128 GB$0.00224
64256 GB$0.00448

For more information see the docs on agent specifications.

Follow Along

For updates on RWX, follow along on X at @rwx_cloud, LinkedIn, or our email newsletter.

Never miss an update

Get the latest releases and news about RWX and our ecosystem with our newsletter.

Share this post

Enjoyed this post? Pleas share it on your favorite social network!

Related posts

Read more on updates and advice from the RWX engineering team

See all posts
Adaptive CI Pipelines with Dynamic Tasks
CI/CD

Adaptive CI Pipelines with Dynamic Tasks

Dynamic tasks enable building CI pipelines which are adaptive based on things like the commit contents or data from external data sources. They unlock a lot of possibilities for building highly performant CI pipelines.

May 31, 2024
Read now
What to Do When Merging Faster than Your Continuous Deployment Process
CI/CD

What to Do When Merging Faster than Your Continuous Deployment Process

When multiple commits are merged in rapid succession, rather than creating a backlog of deployments, a reasonable solution is to skip deploying the earlier commits and only deploy the most recent one.

May 30, 2024
Read now
Implementing a Remote Debugger with Node and tmux
CI/CD

Implementing a Remote Debugger with Node and tmux

We built a remote debugger into Mint using a familiar construct: setting a breakpoint. It's as easy as calling mint-breakpoint from a task and then using the local CLI to run mint debug {debugId}.

May 29, 2024
Read now