Skip to content

Commit ac5388f

Browse files
thomas-tacquetSamyOubouaziznerda-codes
authored
feat(serverless): note about ephemeral storage pricing (#3743)
* feat(serverless): note about ephemeral storage pricing * Apply suggestions from code review Co-authored-by: nerda-codes <[email protected]> --------- Co-authored-by: SamyOubouaziz <[email protected]> Co-authored-by: nerda-codes <[email protected]>
1 parent 3f9ae2e commit ac5388f

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

faq/serverless-containers.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource
2222

2323
* **Memory consumption:** The memory consumption is obtained by multiplying the memory tier chosen by the container run duration.
2424
* **vCPU consumption:** The vCPU consumption is obtained by multiplying the vCPU tier chosen by the container run duration.
25+
* **Ephemeral storage:** Is free of charge, the maximum value of ephemeral storage depends on the memory value.
2526

2627
<Lightbox src={["scaleway-caas-billing-1.webp", "scaleway-caas-billing-2.webp"]} size={"medium"} alt={["Scerverless Containers Billing", "Serverless Containers Billing"]} />
2728

@@ -117,4 +118,4 @@ Containers use http1 by default, yet the gRPC protocol requires http2. You can u
117118
## How does Serverless Container healthcheck work ?
118119

119120
A Serverless Container is set to `ready` once the specified port is correctly bound to the container, and will start receiving traffic. If your application needs to perform some tasks before receiving traffic (e.g. connect to a database), it's important to run them before binding to the port (starting the webserver).
120-
For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the healthcheck will be customizable for your applications.
121+
For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the healthcheck will be customizable for your applications.

faq/serverless-jobs.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Serverless Jobs are billed on a pay-as-you-go basis, strictly on resource consum
2222

2323
* **Memory consumption:** The memory consumption is obtained by multiplying the memory tier chosen by the job run duration.
2424
* **vCPU consumption:** The vCPU consumption is obtained by multiplying the vCPU tier chosen by the job run duration.
25+
* **Ephemeral storage:** Is free of charge, the maximum value of ephemeral storage depends on the memory value.
2526

2627
### Prices
2728

@@ -91,4 +92,4 @@ Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be
9192

9293
## Do Serverless Jobs offer parallelization?
9394

94-
Not yet. Scaleway Serverless Jobs will soon offer parallelization via a `parallelism` parameter for each job. This will automatically launch a given number of replicas of the Job container in parallel.
95+
Not yet. Scaleway Serverless Jobs will soon offer parallelization via a `parallelism` parameter for each job. This will automatically launch a given number of replicas of the Job container in parallel.

0 commit comments

Comments
 (0)