Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -48,3 +48,7 @@ To avoid this, we recommend being cautious when writing temporary files in `/tmp
Applications that rely heavily on temporary file storage should either:
- Use alternative storage paths within your container
- Increase the container's memory allocation to accommodate for temporary file usage

## Sandbox V2 subprocesses RAM usage

Sandbox v2 currently does not support copy-on-write when subprocesses are created, which means that the memory usage of a container is proportional to the number of forked subprocesses. If your application relies on multiple subprocesses that instantiate numerous objects, (such as large modules imports in Python) we recommend using Sandbox v1.
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
title: My container uses too much RAM
description: Troubleshoot issues encountered with Scaleway Serverless Containers consuming excessive amounts of memory.
tags: serverless containers troubleshooting issue error memory ram too much many consumption abnormal high
dates:
validation: 2025-12-19
posted: 2025-12-19
---

## Problem

My container consumes an excessive amount of memory (RAM).

## Possible cause

With [Sandbox v2](/serverless-containers/reference-content/containers-sandbox/), the memory usage of a container is proportional to the number of forked subprocesses.

## Solutions

If your application relies on multiple subprocesses that instantiate numerous objects, (such as large modules imports in Python) we recommend using [Sandbox v1](/serverless-containers/reference-content/containers-sandbox/).

Refer to the [My container runs out of memory (OOM)](/serverless-containers/troubleshooting/container-oom/) for other solutions for memory issues.
1 change: 1 addition & 0 deletions pages/serverless-containers/troubleshooting/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -72,4 +72,5 @@ productIcon: ContainersProductIcon
- [No data show up on Grafana dashboards](/serverless-containers/troubleshooting/no-data-grafana-dashboards/)
- [I get errors when using HTTP/1.0](/serverless-containers/troubleshooting/http1-errors/)
- [My container runs out of memory](/serverless-containers/troubleshooting/container-oom/)
- [My container uses too much RAM](/serverless-containers/troubleshooting/container-uses-too-much-ram/)
</LinksList>
Original file line number Diff line number Diff line change
Expand Up @@ -47,3 +47,7 @@ To avoid this, we recommend being cautious when writing temporary files in `/tmp
Applications that rely heavily on temporary file storage should either:
- Use alternative storage paths within your function
- Increase the function's memory allocation to accommodate for temporary file usage

## Sandbox V2 subprocesses RAM usage

Sandbox v2 currently does not support copy-on-write when subprocesses are created, which means that the memory usage of a function is proportional to the number of forked subprocesses. If your application relies on multiple subprocesses that instantiate numerous objects, (such as large modules imports in Python) we recommend using Sandbox v1.
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
title: My function uses too much RAM
description: Troubleshoot issues encountered with Scaleway Serverless functions consuming excessive amounts of memory.
tags: serverless functions troubleshooting issue error memory ram too much many consumption abnormal high
dates:
validation: 2025-12-19
posted: 2025-12-19
---

## Problem

My function consumes an excessive amount of memory (RAM).

## Possible cause

With [Sandbox v2](/serverless-functions/reference-content/functions-sandbox/), the memory usage of a function is proportional to the number of forked subprocesses.

## Solutions

If your application relies on multiple subprocesses that instantiate numerous objects, (such as large modules imports in Python) we recommend using [Sandbox v1](/serverless-functions/reference-content/functions-sandbox/).

Refer to the [My function runs out of memory (OOM)](/serverless-functions/troubleshooting/function-oom/) for other solutions for memory issues.
3 changes: 2 additions & 1 deletion pages/serverless-functions/troubleshooting/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,7 @@ productIcon: FunctionsProductIcon
- [My function fails after trying too many times](/serverless-functions/troubleshooting/too-many-retries)
- [I am experiencing clock drift with my Serverless Functions](/serverless-functions/troubleshooting/function-clock-drift)
- [I get errors when using HTTP/1.0](/serverless-functions/troubleshooting/http1-errors/)
- [My function runs out of memory](/serverless-containers/troubleshooting/function-oom/)
- [My function runs out of memory](/serverless-functions/troubleshooting/function-oom/)
- [My function uses too much RAM](/serverless-functions/troubleshooting/function-uses-too-much-ram/)

</LinksList>
Loading