Skip to content

Conversation

@Kemi-Elizabeth
Copy link
Collaborator

Why

Closes #5178

What's changed

Improvements to existing autoscaling page (new intro etc) and memory based usage section now visible

Where are changes

Updates are for:

  • platform (sites/platform templates)
  • upsun (sites/upsun templates)

added new intro, use case examples and note about blackfire for users
added memory based autoscaling section
@Kemi-Elizabeth Kemi-Elizabeth linked an issue Nov 6, 2025 that may be closed by this pull request
@github-actions
Copy link

github-actions bot commented Nov 6, 2025

Your Upsun Fixed environment has successfully deployed. 🚀

See the changed pages:

Upsun Fixed docs
Upsun docs

- **Environments:** Configurable per environment - across development, staging, and production

{{< note theme="info" title="Know your app first">}}
Autoscaling is quick to set up: you can [enable it in a few clicks](#enable-autoscaling) from your environment’s **Configure resources** tab. However, because it reacts to real traffic patterns, it’s important to understand your app’s typical performance before turning it on.

Choose a reason for hiding this comment

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

real traffic patterns: this might be misleading... autoscaling on upsun flex does not direclty relate to traffic, only to resources like cpu and memory (usage) for now

changes suggested by Ricardo - adjusted meta description, adjusted thresholds section
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Autoscaling improvements

4 participants