mirror of
https://github.com/fleetdm/fleet
synced 2026-05-06 14:58:33 +00:00
0af5e161d0
* Renaming files and a lot of find and replace * pageRank meta tags, sorting by page rank * reranking * removing numbers * revert changing links that are locked to a commit * update metatag name, uncomment github contributers * Update basic-documentation.page.js * revert link change * more explicit errors, change pageOrderInSection numbers, updated sort * Update build-static-content.js * update comment * update handbook link * handbook entry * update sort * update changelog doc links to use fleetdm.com * move standard query library back to old location, update links/references to location * revert unintentional link changes * Update handbook/community.md Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
76 lines
No EOL
3.5 KiB
Markdown
76 lines
No EOL
3.5 KiB
Markdown
# Load testing
|
|
|
|
The following document outlines the most recent results of a semi-annual load test of the Fleet server.
|
|
|
|
These tests are conducted by the Fleet team, using [osquery-perf](https://github.com/fleetdm/fleet/tree/main/cmd/osquery-perf); a free and open source tool, to generate realistic traffic to the Fleet server.
|
|
|
|
This document reports the minimum resources for successfully running Fleet with 1,000 hosts and 150,000 hosts.
|
|
|
|
## Test parameters
|
|
|
|
The Fleet load tests are conducted with a Fleet server that contains 2 packs, with ~6 queries each, and 6 labels.
|
|
|
|
A test is deemed successful when the Fleet server is able to receive and make requests to the specified number of hosts without over utilizing the specified resources. In addition, a successful test must report that the Fleet server can run a live query against the specified number of hosts.
|
|
|
|
## Results
|
|
|
|
### 1,000 hosts
|
|
|
|
With the following infrastructure, 1,000 hosts successfully communicate with Fleet. The Fleet server is able to run live queries against all hosts.
|
|
|
|
|Fleet instances| CPU Units |RAM |
|
|
|-------|-------------------------|----------------|
|
|
| 1 Fargate task | 256 CPU Units |512 MB of memory|
|
|
|
|
|​| Version |Instance type |
|
|
|-------|-------------------------|--------------|
|
|
| Redis | 5.0.6 |cache.m5.large|
|
|
| MySQL | 5.7.mysql_aurora.2.10.0 | db.t4g.medium|
|
|
|
|
### 150,000 hosts
|
|
|
|
With the infrastructure listed below, 150,000 hosts successfully communicate with Fleet. The Fleet server is able to run live queries against all hosts.
|
|
|
|
|Fleet instance | CPU Units |RAM |
|
|
|-------|-------------------------|----------------|
|
|
| 25 Fargate tasks | 1024 CPU units |2048 MB of memory|
|
|
|
|
|​| Version |Instance type |
|
|
|-------|-------------------------|--------------|
|
|
| Redis | 5.0.6 |cache.m5.large|
|
|
| MySQL | 5.7.mysql_aurora.2.10.0 | db.t4g.medium|
|
|
|
|
The above setup auto scaled based on CPU usage. After a while, the task count ended up in 25 instances even while live querying or adding a new label.
|
|
|
|
## How we are simulating osquery
|
|
|
|
The simulation is run by using [osquery-perf](https://github.com/fleetdm/fleet/tree/main/cmd/osquery-perf), a free and open source tool, to generate realistic traffic to the Fleet server.
|
|
|
|
The following command enrolls and simulates 150,000 hosts on Fleet:
|
|
|
|
```bash
|
|
go run cmd/osquery-perf/agent.go -enroll_secret <secret here> -host_count 150000 -server_url <server URL here> -node_key_file nodekeys
|
|
```
|
|
|
|
After the hosts have been enrolled, you can add `-only_already_enrolled` to make sure the node keys from the file are used and no enrollment happens. This resumes the execution of all the simulated hosts.
|
|
|
|
## Infrastructure setup
|
|
|
|
The deployment of Fleet was done through the example [terraform provided in the repo](https://github.com/fleetdm/fleet/tree/main/tools/terraform) with the following command:
|
|
|
|
```bash
|
|
terraform apply \
|
|
-var domain_fleetctl=<your domain here> \
|
|
-var domain_fleetdm=<alternative domain here> \
|
|
-var s3_bucket=<log bucket name> \
|
|
-var fleet_image="fleetdm/fleet:<tag targeted>" \
|
|
-var vulnerabilities_path="" \
|
|
-var fleet_max_capacity=100 \
|
|
-var fleet_min_capacity=5
|
|
```
|
|
|
|
## Limitations
|
|
|
|
The [osquery-perf](https://github.com/fleetdm/fleet/tree/main/cmd/osquery-perf) tool doesn't simulate all data that's included when a real device communicates to a Fleet instance. For example, system users and software inventory data are not yet simulated by osquery-perf.
|
|
|
|
<meta name="pageOrderInSection" value="500"> |