Skip to content

Commit 97f554d

Browse files
vankovapvankovap
authored
resources update (#200)
1 parent 96a800c commit 97f554d

File tree

33 files changed

+149
-558
lines changed

33 files changed

+149
-558
lines changed

‎apps/docs/content/bun/how-to/create.mdx‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
77
import data from '@site/static/data.json';
88
import UnorderedList from '@site/src/components/UnorderedList';
99
import Video from '/src/components/Video';
10+
import ResourceTable from '/src/components/ResourceTable';
1011

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

@@ -86,11 +87,7 @@ You can choose the CPU mode when starting a new service or change it later. The
8687

8788
Vertical auto scaling has the following default configuration:
8889

89-
|   | Minimum resource | Maximum resource |
90-
| ------------- | ---------------- | ---------------- |
91-
| **CPU cores** | 1 | 5 |
92-
| **RAM** | 0.25 GB | 32 GB |
93-
| **Disk** | 1 GB | 100 GB |
90+
<ResourceTable />
9491

9592
Bun services always start with the minimal resources.
9693

‎apps/docs/content/bun/how-to/scaling.mdx‎

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ description: Get to know how Zerops scales your node.js service.
44
---
55

66
import Image from '/src/components/Image';
7+
import ResourceTable from '/src/components/ResourceTable';
78

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

@@ -66,11 +67,7 @@ The CPU mode doesn't change automatically.
6667

6768
Vertical auto scaling has following default configuration:
6869

69-
| &nbsp; | Minimum resource | Maximum resource |
70-
| ------------- | ---------------- | ---------------- |
71-
| **CPU cores** | 1 | 5 |
72-
| **RAM** | 0.25 GB | 32 GB |
73-
| **Disk** | 1 GB | 100 GB |
70+
<ResourceTable />
7471

7572
Bun service always starts with the minimal resources.
7673

@@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
185182
The **minimum step** for the vertical scaling is
186183

187184
- 1 CPU core
188-
- 0.25 GB RAM
185+
- 0.125 GB RAM
189186
- 0.5 GB disk
190187

191188
When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

‎apps/docs/content/deno/how-to/create.mdx‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
77
import data from '@site/static/data.json';
88
import UnorderedList from '@site/src/components/UnorderedList';
99
import Video from '@site/src/components/Video';
10+
import ResourceTable from '/src/components/ResourceTable';
1011

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

@@ -81,11 +82,7 @@ You can choose the CPU mode when starting a new service or change it later. The
8182

8283
Vertical auto scaling has the following default configuration:
8384

84-
| &nbsp; | Minimum resource | Maximum resource |
85-
| ------------- | ---------------- | ---------------- |
86-
| **CPU cores** | 1 | 5 |
87-
| **RAM** | 0.25 GB | 32 GB |
88-
| **Disk** | 1 GB | 100 GB |
85+
<ResourceTable />
8986

9087
Deno services always start with the minimal resources.
9188

‎apps/docs/content/deno/how-to/scaling.mdx‎

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ description: Get to know how Zerops scales your deno service.
44
---
55

66
import Image from '/src/components/Image';
7+
import ResourceTable from '/src/components/ResourceTable';
78

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

@@ -66,11 +67,7 @@ The CPU mode doesn't change automatically.
6667

6768
Vertical auto scaling has following default configuration:
6869

69-
| &nbsp; | Minimum resource | Maximum resource |
70-
| ------------- | ---------------- | ---------------- |
71-
| **CPU cores** | 1 | 5 |
72-
| **RAM** | 0.25 GB | 32 GB |
73-
| **Disk** | 1 GB | 100 GB |
70+
<ResourceTable />
7471

7572
Deno service always starts with the minimal resources.
7673

@@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
185182
The **minimum step** for the vertical scaling is
186183

187184
- 1 CPU core
188-
- 0.25 GB RAM
185+
- 0.125 GB RAM
189186
- 0.5 GB disk
190187

191188
When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

‎apps/docs/content/dotnet/how-to/create.mdx‎

Lines changed: 2 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
77
import data from '@site/static/data.json';
88
import UnorderedList from '@site/src/components/UnorderedList';
99
import Video from '@site/src/components/Video';
10+
import ResourceTable from '/src/components/ResourceTable';
1011

1112
Zerops provides a .NET runtime service with extensive build support. .NET runtime is highly scalable and customisable to suit both development and production.
1213

@@ -81,32 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode
8182

8283
Vertical auto scaling has following default configuration:
8384

84-
<table className="w-full my-1.5">
85-
<thead>
86-
<tr>
87-
<th className="w-fit"><strong>Resources Type</strong></th>
88-
<th className="w-fit"><strong>Minimum resource</strong></th>
89-
<th className="w-fit"><strong>Maximum resource</strong></th>
90-
</tr>
91-
</thead>
92-
<tbody>
93-
<tr>
94-
<td className="w-fit"><strong>CPU cores</strong></td>
95-
<td className="w-fit">1</td>
96-
<td className="w-fit">5</td>
97-
</tr>
98-
<tr>
99-
<td className="w-fit"><strong>RAM</strong></td>
100-
<td className="w-fit">0.25 GB</td>
101-
<td className="w-fit">32 GB</td>
102-
</tr>
103-
<tr>
104-
<td className="w-fit"><strong>Disk</strong></td>
105-
<td className="w-fit">1 GB</td>
106-
<td className="w-fit">100 GB</td>
107-
</tr>
108-
</tbody>
109-
</table>
85+
<ResourceTable />
11086

11187
.NET service always starts with the minimal resources.
11288

‎apps/docs/content/dotnet/how-to/scaling.mdx‎

Lines changed: 3 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Get to know how Zerops scales your dotnet service.
44
---
55

66
import Image from '/src/components/Image';
7-
7+
import ResourceTable from '/src/components/ResourceTable';
88

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

@@ -68,32 +68,7 @@ The CPU mode doesn't change automatically.
6868

6969
Vertical auto scaling has following default configuration:
7070

71-
<table className="w-full my-1.5">
72-
<thead>
73-
<tr>
74-
<th className="w-fit"><strong>Resources Type</strong></th>
75-
<th className="w-fit"><strong>Minimum resource</strong></th>
76-
<th className="w-fit"><strong>Maximum resource</strong></th>
77-
</tr>
78-
</thead>
79-
<tbody>
80-
<tr>
81-
<td className="w-fit"><strong>CPU cores</strong></td>
82-
<td className="w-fit">1</td>
83-
<td className="w-fit">5</td>
84-
</tr>
85-
<tr>
86-
<td className="w-fit"><strong>RAM</strong></td>
87-
<td className="w-fit">0.25 GB</td>
88-
<td className="w-fit">32 GB</td>
89-
</tr>
90-
<tr>
91-
<td className="w-fit"><strong>Disk</strong></td>
92-
<td className="w-fit">1 GB</td>
93-
<td className="w-fit">100 GB</td>
94-
</tr>
95-
</tbody>
96-
</table>
71+
<ResourceTable />
9772

9873
.NET service always starts with the minimal resources.
9974

@@ -208,7 +183,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
208183
The **minimum step** for the vertical scaling is
209184

210185
- 1 CPU core
211-
- 0.25 GB RAM
186+
- 0.125 GB RAM
212187
- 0.5 GB disk
213188

214189
When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

‎apps/docs/content/elixir/how-to/create.mdx‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
77
import data from '@site/static/data.json';
88
import UnorderedList from '@site/src/components/UnorderedList';
99
import Video from '@site/src/components/Video';
10+
import ResourceTable from '/src/components/ResourceTable';
1011

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

@@ -81,11 +82,7 @@ You can choose the CPU mode when starting a new service or change it later. The
8182

8283
Vertical auto scaling has the following default configuration:
8384

84-
| &nbsp; | Minimum resource | Maximum resource |
85-
| ------------- | ---------------- | ---------------- |
86-
| **CPU cores** | 1 | 5 |
87-
| **RAM** | 0.25 GB | 32 GB |
88-
| **Disk** | 1 GB | 100 GB |
85+
<ResourceTable />
8986

9087
Elixir services always start with the minimal resources.
9188

‎apps/docs/content/elixir/how-to/scaling.mdx‎

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ description: Get to know how Zerops scales your Elixir service.
44
---
55

66
import Image from '/src/components/Image';
7+
import ResourceTable from '/src/components/ResourceTable';
78

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

@@ -66,11 +67,7 @@ The CPU mode doesn't change automatically.
6667

6768
Vertical auto scaling has following default configuration:
6869

69-
| &nbsp; | Minimum resource | Maximum resource |
70-
| ------------- | ---------------- | ---------------- |
71-
| **CPU cores** | 1 | 5 |
72-
| **RAM** | 0.25 GB | 32 GB |
73-
| **Disk** | 1 GB | 100 GB |
70+
<ResourceTable />
7471

7572
Elixir service always starts with the minimal resources.
7673

@@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
185182
The **minimum step** for the vertical scaling is
186183

187184
- 1 CPU core
188-
- 0.25 GB RAM
185+
- 0.125 GB RAM
189186
- 0.5 GB disk
190187

191188
When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

‎apps/docs/content/frameworks/laravel.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ import IconTwill from '@theme/Icon/Twill';
1414
Zerops implements what we call "transparent infrastructure" - you get enterprise-grade capabilities with development-friendly ergonomics. This means:
1515

1616
- **Full system access** across all environments
17-
- **Granular resource control** starting at 0.25GB RAM
17+
- **Granular resource control** starting at 0.125GB RAM
1818
- **True environment parity** from local to production
1919
- **Zero-downtime deployments** by default
2020

‎apps/docs/content/gleam/how-to/create.mdx‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
77
import data from '@site/static/data.json';
88
import UnorderedList from '@site/src/components/UnorderedList';
99
import Video from '@site/src/components/Video';
10+
import ResourceTable from '/src/components/ResourceTable';
1011

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

@@ -82,11 +83,7 @@ You can choose the CPU mode when starting a new service or change it later. The
8283

8384
Vertical auto scaling has the following default configuration:
8485

85-
| &nbsp; | Minimum resource | Maximum resource |
86-
| ------------- | ---------------- | ---------------- |
87-
| **CPU cores** | 1 | 5 |
88-
| **RAM** | 0.25 GB | 32 GB |
89-
| **Disk** | 1 GB | 100 GB |
86+
<ResourceTable />
9087

9188
Gleam services always start with the minimal resources.
9289

0 commit comments

Comments
 (0)