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.

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

RDoc-3011 & RDoc-3012 Add autoscaling feature description #1918

Merged
merged 2 commits into from
Oct 29, 2024

Conversation

hiddenshadow21
Copy link
Contributor

@hiddenshadow21 hiddenshadow21 commented Oct 3, 2024

@hiddenshadow21 hiddenshadow21 changed the title RDoc-3012 Add autoscaling feature description RDoc-3011 & RDoc-3012 Add autoscaling feature description Oct 3, 2024
@PFYasu PFYasu added the Cloud label Oct 3, 2024
|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling |
| Upscaling Grace Period | The time delay before upscaling begins after a high resource threshold is exceeded, allowing the system to avoid immediate scaling. |
| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. |
Copy link
Contributor

@PFYasu PFYasu Oct 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. |
| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. |


| Parameter | Description |
|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling |
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling. |

| Upscaling Grace Period | The time delay before upscaling begins after a high resource threshold is exceeded, allowing the system to avoid immediate scaling. |
| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. |
| High Cpu Threshold Duration | The duration for which the average CPU usage must exceed the threshold before triggering upscaling. |
| Upscaling Step | Determines by how many instances upscaling should take place in one go. For example with step set to 2 it will scale up from *Dev10* to *Dev30* |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| Upscaling Step | Determines by how many instances upscaling should take place in one go. For example with step set to 2 it will scale up from *Dev10* to *Dev30* |
| Upscaling Step | Determines by how many instances upscaling should take place in one go. For example with step set to 2 it will scale up from *Dev10* to *Dev30*. |

@ppekrol ppekrol merged commit 45354da into ravendb:master Oct 29, 2024
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants