Skip to content

feat(serverless): note about ephemeral storage pricing #3743

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 25, 2024
Merged

feat(serverless): note about ephemeral storage pricing #3743

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
79e163a
feat(serverless): note about ephemeral storage pricing
thomas-tacquet Sep 24, 2024
bb90e69
Apply suggestions from code review
SamyOubouaziz Sep 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion faq/serverless-containers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource

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

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

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

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).
For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the healthcheck will be customizable for your applications.
For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the healthcheck will be customizable for your applications.
3 changes: 2 additions & 1 deletion faq/serverless-jobs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ Serverless Jobs are billed on a pay-as-you-go basis, strictly on resource consum

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

### Prices

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

## Do Serverless Jobs offer parallelization?

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.
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.