> For the complete documentation index, see [llms.txt](https://bonusmastodon.aus.social/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bonusmastodon.aus.social/basics/cloud-servers-vms.md).

# Cloud Servers (VMs)

VMs are generally pretty “affordable” these days.. But if you’re planning to scale to thousands of concurrent people on your instance, you will likely find yourself having multiple VMs.

Our goal with this guide is to optimise the VMs to run as high performance as possible on hopefully the smallest instances we can use.

## Example: 

Aus.Social currently has too many VMs, but for reference:

* PostgreSQL and Redis : 4 CPU / 8 GB VM
* ElasticSearch : 2 CPU / 4 GB VM
* Sidekiq : 6 CPU / 16 GB VM
* Nginx: 2 CPU / 4GB VM
* Puma/Streaming : Two x 4 CPU / 8 GB VM

This setup will allow me to increase the VMs as required but is currently running at around 50% utilisation on the Nginx / web server when hosting 10,000\~ active users (with average on and off usage).

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bonusmastodon.aus.social/basics/cloud-servers-vms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.