diff --git a/apps/docs/content/bun/how-to/create.mdx b/apps/docs/content/bun/how-to/create.mdx index f5e37ca0..a7dba69d 100644 --- a/apps/docs/content/bun/how-to/create.mdx +++ b/apps/docs/content/bun/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a powerful Bun runtime service with extensive build support. The Bun runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Bun environment up and running in no time. @@ -86,11 +87,7 @@ You can choose the CPU mode when starting a new service or change it later. The Vertical auto scaling has the following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + Bun services always start with the minimal resources. diff --git a/apps/docs/content/bun/how-to/scaling.mdx b/apps/docs/content/bun/how-to/scaling.mdx index ea6b0106..52d2f8aa 100644 --- a/apps/docs/content/bun/how-to/scaling.mdx +++ b/apps/docs/content/bun/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your node.js service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,11 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + Bun service always starts with the minimal resources. @@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/deno/how-to/create.mdx b/apps/docs/content/deno/how-to/create.mdx index 40204db2..a9b882f2 100644 --- a/apps/docs/content/deno/how-to/create.mdx +++ b/apps/docs/content/deno/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a powerful Deno runtime service with extensive build support. The Deno runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Deno environment up and running in no time. @@ -81,11 +82,7 @@ You can choose the CPU mode when starting a new service or change it later. The Vertical auto scaling has the following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + Deno services always start with the minimal resources. diff --git a/apps/docs/content/deno/how-to/scaling.mdx b/apps/docs/content/deno/how-to/scaling.mdx index d038e1ba..352f0966 100644 --- a/apps/docs/content/deno/how-to/scaling.mdx +++ b/apps/docs/content/deno/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your deno service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,11 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + Deno service always starts with the minimal resources. @@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/dotnet/how-to/create.mdx b/apps/docs/content/dotnet/how-to/create.mdx index 5507f634..9d6dcc2c 100644 --- a/apps/docs/content/dotnet/how-to/create.mdx +++ b/apps/docs/content/dotnet/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a .NET runtime service with extensive build support. .NET runtime is highly scalable and customisable to suit both development and production. @@ -81,32 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
+ .NET service always starts with the minimal resources. diff --git a/apps/docs/content/dotnet/how-to/scaling.mdx b/apps/docs/content/dotnet/how-to/scaling.mdx index c9374dfb..cf7bb3f1 100644 --- a/apps/docs/content/dotnet/how-to/scaling.mdx +++ b/apps/docs/content/dotnet/how-to/scaling.mdx @@ -4,7 +4,7 @@ description: Get to know how Zerops scales your dotnet service. --- import Image from '/src/components/Image'; - +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -68,32 +68,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
+ .NET service always starts with the minimal resources. @@ -208,7 +183,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/elixir/how-to/create.mdx b/apps/docs/content/elixir/how-to/create.mdx index 810a3b2e..70223f4f 100644 --- a/apps/docs/content/elixir/how-to/create.mdx +++ b/apps/docs/content/elixir/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a powerful Elixir runtime service with extensive build support. The Elixir runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Elixir environment up and running in no time. @@ -81,11 +82,7 @@ You can choose the CPU mode when starting a new service or change it later. The Vertical auto scaling has the following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + Elixir services always start with the minimal resources. diff --git a/apps/docs/content/elixir/how-to/scaling.mdx b/apps/docs/content/elixir/how-to/scaling.mdx index 369a12a4..0087c20f 100644 --- a/apps/docs/content/elixir/how-to/scaling.mdx +++ b/apps/docs/content/elixir/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your Elixir service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,11 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + Elixir service always starts with the minimal resources. @@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/frameworks/laravel.mdx b/apps/docs/content/frameworks/laravel.mdx index f07f123d..dd446290 100644 --- a/apps/docs/content/frameworks/laravel.mdx +++ b/apps/docs/content/frameworks/laravel.mdx @@ -14,7 +14,7 @@ import IconTwill from '@theme/Icon/Twill'; Zerops implements what we call "transparent infrastructure" - you get enterprise-grade capabilities with development-friendly ergonomics. This means: - **Full system access** across all environments -- **Granular resource control** starting at 0.25GB RAM +- **Granular resource control** starting at 0.125GB RAM - **True environment parity** from local to production - **Zero-downtime deployments** by default diff --git a/apps/docs/content/gleam/how-to/create.mdx b/apps/docs/content/gleam/how-to/create.mdx index 8cca87d4..aeb4a4d4 100644 --- a/apps/docs/content/gleam/how-to/create.mdx +++ b/apps/docs/content/gleam/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a powerful Gleam runtime service with extensive build support. The Gleam runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Gleam environment up and running in no time. @@ -82,11 +83,7 @@ You can choose the CPU mode when starting a new service or change it later. The Vertical auto scaling has the following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + Gleam services always start with the minimal resources. diff --git a/apps/docs/content/gleam/how-to/scaling.mdx b/apps/docs/content/gleam/how-to/scaling.mdx index f2a369b5..c4e197f4 100644 --- a/apps/docs/content/gleam/how-to/scaling.mdx +++ b/apps/docs/content/gleam/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your Gleam service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,11 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + Gleam service always starts with the minimal resources. @@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/go/how-to/create.mdx b/apps/docs/content/go/how-to/create.mdx index e28a1956..25bd55e7 100644 --- a/apps/docs/content/go/how-to/create.mdx +++ b/apps/docs/content/go/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a Go runtime service with extensive build support. Go runtime is highly scalable and customisable to suit both development and production. @@ -81,32 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
+ Go service always starts with the minimal resources. diff --git a/apps/docs/content/go/how-to/scaling.mdx b/apps/docs/content/go/how-to/scaling.mdx index e614ef80..ebcb9401 100644 --- a/apps/docs/content/go/how-to/scaling.mdx +++ b/apps/docs/content/go/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your go service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,33 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Go service always starts with the minimal resources. @@ -207,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/homepage.mdx b/apps/docs/content/homepage.mdx index af64c8d0..5ab99bc3 100644 --- a/apps/docs/content/homepage.mdx +++ b/apps/docs/content/homepage.mdx @@ -164,7 +164,7 @@ You get a fully managed, professional infrastructure setup that will scale no ma ### ➡️ Granular resource configuration, autoscaling and high availability of services -Zerops has fully automatic horizontal and vertical scaling with configuration steps as small as 0.25 MB RAM and 1 CPU core. Your runtime services can go from a single container with 0.25 RAM and 1 CPU core to 10 containers each with 32 GB RAM and 10 CPU cores and then back in a matter of minutes. At the same time, all database and storage services are offered in well-crafted setups that go through performance optimizations while scaling and are available in both non-HA (single container) and high availability (multiple containers and balancers) modes. +Zerops has fully automatic horizontal and vertical scaling with configuration steps as small as 0.125 GB RAM and 1 CPU core. Your runtime services can go from a single container with 0.25 RAM and 1 CPU core to 10 containers each with 32 GB RAM and 10 CPU cores and then back in a matter of minutes. At the same time, all database and storage services are offered in well-crafted setups that go through performance optimizations while scaling and are available in both non-HA (single container) and high availability (multiple containers and balancers) modes. :::tip[**What does this mean for you?**] diff --git a/apps/docs/content/java/how-to/create.mdx b/apps/docs/content/java/how-to/create.mdx index c31928ad..283d7e9e 100644 --- a/apps/docs/content/java/how-to/create.mdx +++ b/apps/docs/content/java/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a Java runtime service with extensive build support. Java runtime is highly scalable and customisable to suit both development and production. @@ -81,33 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Java service always starts with the minimal resources. diff --git a/apps/docs/content/java/how-to/scaling.mdx b/apps/docs/content/java/how-to/scaling.mdx index c46ce620..20393fd3 100644 --- a/apps/docs/content/java/how-to/scaling.mdx +++ b/apps/docs/content/java/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your java service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,33 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Java service always starts with the minimal resources. @@ -207,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/keydb/how-to/create.mdx b/apps/docs/content/keydb/how-to/create.mdx index 3450046c..5fd57eb9 100644 --- a/apps/docs/content/keydb/how-to/create.mdx +++ b/apps/docs/content/keydb/how-to/create.mdx @@ -5,6 +5,7 @@ description: Learn how you can create a keydb service in Zerops. import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; +import ResourceTable from '/src/components/ResourceTable'; [KeyDB ↗](https://docs.keydb.dev/) is a fully open source database, backed by Snap, and a faster drop in alternative to Redis. @@ -101,33 +102,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + For most cases, the default parameters will work without issues. If you need to limit the cost of the KeyDB service, lower the maximal resources. Zerops will never scale above the selected maximums. diff --git a/apps/docs/content/keydb/how-to/scale.mdx b/apps/docs/content/keydb/how-to/scale.mdx index db07359b..843e15ab 100644 --- a/apps/docs/content/keydb/how-to/scale.mdx +++ b/apps/docs/content/keydb/how-to/scale.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your keydb service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your database based on its usage. If the current use of your database does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your database is under heavy load or needs to store more data, then auto scaling increases the resources for the database to make sure it runs smoothly. @@ -38,33 +39,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + For most cases, the default parameters will work without issues. If you need to limit the cost of the KeyDB service, lower the maximal resources. Zerops will never scale above the selected maximums. @@ -128,7 +103,7 @@ Zerops monitors CPU, RAM and Disk usage in all running containers each 10 second The **scale up threshold** is derived from following **minimum free resources**: - 0.1 CPU core -- 0.25 GB RAM (You can [fine tune](#fine-tune-the-auto-scaling) this setting) +- 62.5 MB RAM (You can [fine tune](#fine-tune-the-auto-scaling) this setting) - 0.5 GB disk If the minimum free CPU, RAM or disk usage of a container is lower than the defined scale up threshold, Zerops scales the container up. @@ -138,7 +113,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the database is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/mariadb/how-to/create.mdx b/apps/docs/content/mariadb/how-to/create.mdx index 5f1bdd97..8921bf94 100644 --- a/apps/docs/content/mariadb/how-to/create.mdx +++ b/apps/docs/content/mariadb/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import Video from '@site/src/components/Video'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; +import ResourceTable from '/src/components/ResourceTable'; MariaDB is the open source relational database loved by developers all over the world. Created by MySQL’s original developers, MariaDB is compatible with MySQL and guaranteed to stay open source forever. @@ -109,6 +110,12 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: + + diff --git a/apps/docs/content/mariadb/how-to/scale.mdx b/apps/docs/content/mariadb/how-to/scale.mdx index aa305403..38d962bc 100644 --- a/apps/docs/content/mariadb/how-to/scale.mdx +++ b/apps/docs/content/mariadb/how-to/scale.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your mariadb service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your database based on its usage. If the current use of your database does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your database is under heavy load or needs to store more data, then auto scaling increases the resources for the database to make sure it runs smoothly. @@ -38,11 +39,11 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.5 GB | 32 GB | -| **Disk** | 1 GB | 100 GB | + For most cases, the default parameters will work without issues. If you need to limit the cost of the MariaDB service, lower the maximal resources. Zerops will never scale above the selected maximums. @@ -106,7 +107,7 @@ Zerops monitors CPU, RAM and Disk usage in all running containers each 10 second The **scale up threshold** is derived from following **minimum free resources**: - 0.1 CPU core -- 0.25 GB RAM (You can [fine tune](#fine-tune-the-auto-scaling) this setting) +- 0.125 GB RAM (You can [fine tune](#fine-tune-the-auto-scaling) this setting) - 0.5 GB disk If the minimum free CPU, RAM or disk usage of a container is lower than the defined scale up threshold, Zerops scales the container up. @@ -116,7 +117,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the database is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/nginx/how-to/create.mdx b/apps/docs/content/nginx/how-to/create.mdx index fcd27efe..bc9a04ca 100644 --- a/apps/docs/content/nginx/how-to/create.mdx +++ b/apps/docs/content/nginx/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; The Nginx static service contains the Nginx web server optimized for your static content. Nginx static service is highly scalable and customisable to suit both development and production. @@ -81,33 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: -
- - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Nginx static service always starts with the minimal resources. diff --git a/apps/docs/content/nginx/how-to/scaling.mdx b/apps/docs/content/nginx/how-to/scaling.mdx index ef431f77..34c81c58 100644 --- a/apps/docs/content/nginx/how-to/scaling.mdx +++ b/apps/docs/content/nginx/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your nginx service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,33 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Nginx static service always starts with the minimal resources. @@ -197,7 +172,7 @@ Zerops monitors CPU, RAM and Disk usage in all running containers each 10 second The **scale up threshold** is derived from following **minimum free resources**: - 0.1 CPU core -- 0.125 GB RAM (You can [fine tune](#fine-tune-the-auto-scaling) this setting) +- 62.5 MB RAM (You can [fine tune](#fine-tune-the-auto-scaling) this setting) - 0.5 GB disk If the minimum free CPU, RAM or disk usage of a container is lower than the defined scale up threshold, Zerops scales the container up. @@ -207,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/nodejs/how-to/create.mdx b/apps/docs/content/nodejs/how-to/create.mdx index f5124b95..13c2e1e4 100644 --- a/apps/docs/content/nodejs/how-to/create.mdx +++ b/apps/docs/content/nodejs/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a powerful Node.js runtime service with extensive build support. The Node.js runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Node.js environment up and running in no time. @@ -81,32 +82,7 @@ You can choose the CPU mode when starting a new service or change it later. The Vertical auto scaling has the following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
+ Node.js services always start with the minimal resources. diff --git a/apps/docs/content/nodejs/how-to/scaling.mdx b/apps/docs/content/nodejs/how-to/scaling.mdx index 9cb57429..6b4278af 100644 --- a/apps/docs/content/nodejs/how-to/scaling.mdx +++ b/apps/docs/content/nodejs/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your node.js service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,33 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Node.js service always starts with the minimal resources. @@ -207,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/php/how-to/create.mdx b/apps/docs/content/php/how-to/create.mdx index 7fc7143b..7ccffc14 100644 --- a/apps/docs/content/php/how-to/create.mdx +++ b/apps/docs/content/php/how-to/create.mdx @@ -6,6 +6,7 @@ description: Learn how you can create a php service in Zerops. import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides 2 PHP services with an included web server: **PHP+Nginx** and **PHP+Apache**. PHP runtime is highly scalable and customisable to suit both development and production. @@ -77,33 +78,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + PHP service always starts with the minimal resources. diff --git a/apps/docs/content/php/how-to/scaling.mdx b/apps/docs/content/php/how-to/scaling.mdx index 965dbb1a..ab6c55f0 100644 --- a/apps/docs/content/php/how-to/scaling.mdx +++ b/apps/docs/content/php/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your php service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,33 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + PHP service always starts with the minimal resources. @@ -207,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/postgresql/how-to/create.mdx b/apps/docs/content/postgresql/how-to/create.mdx index 595c6725..73497a11 100644 --- a/apps/docs/content/postgresql/how-to/create.mdx +++ b/apps/docs/content/postgresql/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; ## Create PostgreSQL using Zerops GUI @@ -106,11 +107,11 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto-scaling has the following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 8 GB | -| **Disk** | 1 GB | 2.5 GB | + For most cases, the default parameters will work without issues. If you need to limit the cost of the PostgreSQL service, lower the maximal resources. Zerops will never scale above the selected maximums. diff --git a/apps/docs/content/postgresql/how-to/scale.mdx b/apps/docs/content/postgresql/how-to/scale.mdx index 53d3325e..c8bcd9a8 100644 --- a/apps/docs/content/postgresql/how-to/scale.mdx +++ b/apps/docs/content/postgresql/how-to/scale.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your postgresql service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your database based on its usage. If the current use of your database does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your database is under heavy load or needs to store more data, then auto scaling increases the resources for the database to make sure it runs smoothly. @@ -38,11 +39,11 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: -|   | Minimum resource | Maximum resource | -| ------------- | ---------------- | ---------------- | -| **CPU cores** | 1 | 5 | -| **RAM** | 0.25 GB | 8 GB | -| **Disk** | 1 GB | 2.5 GB | + For most cases, the default parameters will work without issues. If you need to limit the cost of the PostgreSQL service, lower the maximal resources. Zerops will never scale above the selected maximums. @@ -106,7 +107,7 @@ Zerops monitors CPU, RAM and Disk usage in all running containers each 10 second The **scale up threshold** is derived from following **minimum free resources**: - 0.1 CPU core -- 0.25 GB RAM (You can [fine tune](#fine-tune-the-auto-scaling) this setting) +- 0.125 GB RAM (You can [fine tune](#fine-tune-the-auto-scaling) this setting) - 0.5 GB disk If the minimum free CPU, RAM or disk usage of a container is lower than the defined scale up threshold, Zerops scales the container up. @@ -116,7 +117,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the database is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/python/how-to/create.mdx b/apps/docs/content/python/how-to/create.mdx index a0ce080a..c5840aa0 100644 --- a/apps/docs/content/python/how-to/create.mdx +++ b/apps/docs/content/python/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a Python runtime service with extensive build support. Python runtime is highly scalable and customisable to suit both development and production. @@ -81,32 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk5 GB100 GB
+ Python service always starts with the minimal resources. diff --git a/apps/docs/content/python/how-to/scaling.mdx b/apps/docs/content/python/how-to/scaling.mdx index 49def995..9b7a9dcc 100644 --- a/apps/docs/content/python/how-to/scaling.mdx +++ b/apps/docs/content/python/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your python service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,33 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Python service always starts with the minimal resources. @@ -207,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/content/rust/how-to/create.mdx b/apps/docs/content/rust/how-to/create.mdx index ee1887d8..7f93c9ec 100644 --- a/apps/docs/content/rust/how-to/create.mdx +++ b/apps/docs/content/rust/how-to/create.mdx @@ -7,6 +7,7 @@ import Image from '/src/components/Image'; import data from '@site/static/data.json'; import UnorderedList from '@site/src/components/UnorderedList'; import Video from '@site/src/components/Video'; +import ResourceTable from '/src/components/ResourceTable'; Zerops provides a Rust runtime service with extensive build support. Rust runtime is highly scalable and customisable to suit both development and production. @@ -81,33 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Rust service always starts with the minimal resources. diff --git a/apps/docs/content/rust/how-to/scaling.mdx b/apps/docs/content/rust/how-to/scaling.mdx index 7ca92820..3b528d48 100644 --- a/apps/docs/content/rust/how-to/scaling.mdx +++ b/apps/docs/content/rust/how-to/scaling.mdx @@ -4,6 +4,7 @@ description: Get to know how Zerops scales your rust service. --- import Image from '/src/components/Image'; +import ResourceTable from '/src/components/ResourceTable'; Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly. @@ -66,33 +67,7 @@ The CPU mode doesn't change automatically. Vertical auto scaling has following default configuration: - - - - - - - - - - - - - - - - - - - - - - - - - -
Resources TypeMinimum resourceMaximum resource
CPU cores15
RAM0.25 GB32 GB
Disk1 GB100 GB
- + Rust service always starts with the minimal resources. @@ -207,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b The **minimum step** for the vertical scaling is - 1 CPU core -- 0.25 GB RAM +- 0.125 GB RAM - 0.5 GB disk When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically. diff --git a/apps/docs/src/components/ResourceTable/index.tsx b/apps/docs/src/components/ResourceTable/index.tsx new file mode 100644 index 00000000..ff5e82b2 --- /dev/null +++ b/apps/docs/src/components/ResourceTable/index.tsx @@ -0,0 +1,51 @@ +import React from 'react'; + +const DEFAULT_RESOURCES = { + cpu: { + name: 'CPU cores', + min: '1', + max: '5' + }, + ram: { + name: 'RAM', + min: '0.125 GB', + max: '32 GB' + }, + disk: { + name: 'Disk', + min: '1 GB', + max: '100 GB' + } +}; + +const ResourceTable = ({ resources = {} }) => { + // Merge provided resources with defaults + const finalResources = { + cpu: { ...DEFAULT_RESOURCES.cpu, ...resources.cpu }, + ram: { ...DEFAULT_RESOURCES.ram, ...resources.ram }, + disk: { ...DEFAULT_RESOURCES.disk, ...resources.disk } + }; + + return ( + + + + + + + + + + {Object.values(finalResources).map((resource, index) => ( + + + + + + ))} + +
 MinimumMaximum
{resource.name}{resource.min}{resource.max}
+ ); +}; + +export default ResourceTable; \ No newline at end of file