Skip to content

Commit

Permalink
Add notes on max vCPU
Browse files Browse the repository at this point in the history
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
  • Loading branch information
alexellis committed Oct 6, 2023
1 parent bbdb64b commit 35cbfac
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion docs/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,11 @@ If you suspect a job is running out of RAM or would benefit from more vCPU, you
+runs-on: actuated-16gb-8cpu
```

You must set both RAM and vCPU at the same time. For arm64 builds, the format follows the same convention: `actuated-arm64-16gb-8cpu`.
You must set both RAM and vCPU at the same time. For arm64 builds, the format follows the same convention: `actuated-arm64-16gb-8cpu`.'

Bear in mind that if you set the RAM higher than the default, this may result in fewer concurrent VMs being scheduled on a single server.

The maximum amount of vCPU that can be set for a single job is 32 vCPU, this is an implementation detail of Firecracker and may change in the future.

### Running out of disk space for jobs

Expand Down

0 comments on commit 35cbfac

Please sign in to comment.