Skip to content
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

documentation update #95

Merged
merged 3 commits into from
Dec 5, 2023
Merged

documentation update #95

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5246b2c
documentation update
Dec 1, 2023
b93f87e
Improve scalability page.
judu Dec 5, 2023
7f1d37f
Update content/doc/administrate/scalability.md
judu Dec 5, 2023
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
5 changes: 5 additions & 0 deletions content/doc/CLI/manage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,11 @@ clever env set <variable-name> <variable-value>
# Remove an environment variable
clever env rm <variable-name>
```
If your environment variable contains a `-`, then write: `clever env set test -- ---foo---`

Or you can put the dashes before the remaining arguments, as follows: `clever -- env set test ---bar---`

The `--` indicates that there are no options to be parsed.

### Load environment variables

Expand Down
2 changes: 1 addition & 1 deletion content/doc/administrate/log-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ type: docs
Log management is currently only available through our API and [clever-tools]({{< ref "/doc/CLI" >}}).

{{< callout type="info">}}
Logs are currently retained for a maximum of 1 day. Logs are flushed daily at midnight.
Logs are currently retained for a maximum of 7 days. Logs are flushed daily at midnight.
You can use log drains if a greater retention is needed.
{{< /callout >}}

Expand Down
23 changes: 14 additions & 9 deletions content/doc/administrate/scalability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,22 +43,27 @@ In case of large traffic, we detect a high load on your application and spawn **
This will automatically set up another identical application with same size. Both will run in parallel with load
balancing. If the traffic grows even more, we will repeat the process until the maximum instances count you defined.

{{< callout type="info" >}}
The maximum number of Scalers you can set for an application is 40.
{{< /callout >}}

This process is exactly the opposite when the **load decreases**. A Scaler is removed and so on till a **minimum
reasonable level** is reached.

The following scheme depicts a Scaler replication in case of a load increase:

{{< image "/images/doc/scaling_horizontal_scheme.jpg" "You can manage the range of Scalers you consider in the application configurator. The range is from 1 to 40." >}}
{{< image "/images/doc/scaling_horizontal_scheme.jpg" "Horizontal scaling: you can define the min and max numbers of Scalers you need." >}}

You can manage the range of Scalers you consider in the application configurator. The range is from 1 to 20.

{{< image "/images/doc/select-scalab-horizontal.png" "Horizontal scaling: the amount of scaler will increase and the sclaer size will vary between XS and S" >}}
{{< image "/images/doc/select-scalab-horizontal.png" "Horizontal scaling: the amount of Scalers will evolve between 1 and 15." >}}

## Vertical scaling

In case of large traffic, we detect a high load on your application and set up **a new larger Scaler**.

{{< callout type="info" >}}
The maximum Scaler size is 3XL: 16 vCPUs and 32 GiB of memory.
{{< /callout >}}

In case of low traffic, we detect a low load and set up **a new smaller Scaler**.

You give more power to your application by setting up a larger instance that will replace the previous one. The more the
Expand All @@ -68,17 +73,17 @@ The following scheme depicts a larger Scaler replacement in case of a load incre

{{< image "/images/doc/scaling_vertical_scheme.jpg" "vertical scaling" >}}

You can choose the type of Scalers you consider by defining a maximum instance size manually or just let Clever Cloud choose for you by defining nothing:
You can choose the size of Scalers you want by defining a maximum instance size manually:

{{< image "/images/doc/select-scalab.png" "Vertical scaling: the scaler size will from S to XL." >}}
{{< image "/images/doc/select-scalab.png" "Vertical scaling: the Scaler size will go from S to XL." >}}

## Combination of both scalings

When both scalings are set up, **vertical scaling** is privileged over **horizontal scaling**. In the case you set the
vertical scaling from S to L, and the horizontal scaling from 2 scalers to 4 scalers, Clever Cloud will firstly increase
the size of the 2 scalers already launched.
vertical scaling from S to L, and the horizontal scaling from 2 Scalers to 4 Scalers, Clever Cloud will firstly increase
the size of the 2 Scalers already launched.

If the 2 initials scalers are at their maximum size, Clever Cloud will launch new scalers with the maximum size of scalers.
If the 2 initials Scalers are at their maximum size, Clever Cloud will launch new Scalers with the maximum Scalers size.
This is how it'll be done:

2-S => 2-M => 2-L => 3-L => 4-L.
Loading