Les pubs vous déplaisent ? Aller Sans pub Auj. 

Calculateur de ressources de conteneur Docker

DonnéesPromoteur

PUBLICITÉ · RETIRER?

SAISIR

Processus automatique

SORTIR

Côté client

Propriété	Valeur
Requête CPU	-
Limite CPU	-
Requête CPU (millicœurs)	-
Limite CPU (millicœurs)	-
Requête mémoire	-
Limite mémoire	-
CPU total (tous les conteneurs)	-
Mémoire totale (tous les conteneurs)	-

Commande Docker Run

Indicateurs Docker --memory et --cpus

YAML Kubernetes

Kubernetes resources.requests / limits

PUBLICITÉ · RETIRER?

Guide

Calculateur de ressources de conteneur Docker

Quickly calculate recommended CPU and memory resource limits for Docker containers and Kubernetes deployments. Select a workload type, enter your host resources, and get precise values for Docker run flags and Kubernetes resource manifests — no guesswork required.

Comment utiliser

Select a workload type (web server, database, cache, ML inference, or custom)
Enter your host CPU cores et RAM in GB
Set the number of containers to split resources across
View the calculated resource table, Docker run command, and Kubernetes YAML

Caractéristiques

Workload Presets – Built-in resource profiles for common workloads: web server, background worker, database, cache, and ML inference
Custom Mode – Define your own CPU and memory request/limit values
Multi-Container Splitting – Automatically divides host resources across multiple containers
Avertissements de capacité – Alerts you when total resource limits exceed host capacity
Indicateurs Docker Run – Generates ready-to-use –memory and –cpus flags
YAML Kubernetes – Outputs resources.requests and resources.limits in YAML format with millicores
Auto-Calculate – Results update instantly as you change inputs

 FAQ

What is the difference between resource requests and limits in Kubernetes?

Resource requests define the minimum resources a container needs to be scheduled on a node. Limits define the maximum resources a container can use. If a container exceeds its memory limit, it gets killed (OOMKilled). If it exceeds CPU limits, it gets throttled.
How do Docker --memory and --cpus flags work?

The --memory flag sets a hard memory limit for the container. If the process inside tries to use more, Docker kills it. The --cpus flag limits how much CPU time the container can use — for example, --cpus=0.5 means the container can use 50% of one CPU core.
What are millicores in Kubernetes?

Millicores are a way to express fractional CPU resources. 1 CPU core equals 1000 millicores (1000m). So 250m means 25% of one CPU core. This allows fine-grained resource allocation for containers that don't need a full core.
Why should I set resource limits on containers?

Without resource limits, a single container can consume all available host resources, starving other containers. Setting limits ensures fair resource distribution, prevents out-of-memory crashes from affecting the host, and is required for Kubernetes Quality of Service (QoS) classes.

Envie d'une expérience sans pub ? Passez à la version sans pub



 Installez nos extensions

Ajoutez des outils IO à votre navigateur préféré pour un accès instantané et une recherche plus rapide

Sur

恵 Le Tableau de Bord Est Arrivé !

Tableau de Bord est une façon amusante de suivre vos jeux, toutes les données sont stockées dans votre navigateur. D'autres fonctionnalités arrivent bientôt !

PUBLICITÉ · RETIRER?