Skip to content

Commit

Permalink
longevity test results for oss and plus
Browse files Browse the repository at this point in the history
  • Loading branch information
salonichf5 committed Nov 13, 2024
1 parent 16705c4 commit d583741
Show file tree
Hide file tree
Showing 13 changed files with 193 additions and 0 deletions.
Binary file added tests/results/longevity/1.5.0/oss-cpu.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added tests/results/longevity/1.5.0/oss-memory.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added tests/results/longevity/1.5.0/oss-ngf-memory.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added tests/results/longevity/1.5.0/oss-reloads.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
97 changes: 97 additions & 0 deletions tests/results/longevity/1.5.0/oss.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,97 @@
# Results

## Test environment

NGINX Plus: false

NGINX Gateway Fabric:

- Commit: 36f245bcba55935064324ff5803d66110117f7da
- Date: 2024-11-08T19:20:48Z
- Dirty: false

GKE Cluster:

- Node count: 2
- k8s version: v1.30.5-gke.1443001
- vCPUs per node: 2
- RAM per node: 4018120Ki
- Max pods per node: 110
- Zone: us-west2-a
- Instance Type: e2-medium

## Traffic

HTTP:

```text
Running 5760m test @ http://cafe.example.com/coffee
2 threads and 100 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 236.88ms 177.22ms 2.00s 72.93%
Req/Sec 232.09 156.40 1.90k 66.16%
156451087 requests in 5760.00m, 53.52GB read
Socket errors: connect 0, read 350645, write 0, timeout 75472
Requests/sec: 452.69
Transfer/sec: 162.39KB
KB
```

HTTPS:

```text
Running 5760m test @ https://cafe.example.com/tea
2 threads and 100 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 223.09ms 138.95ms 2.00s 63.95%
Req/Sec 230.23 155.14 1.80k 66.18%
155166081 requests in 5760.00m, 52.20GB read
Socket errors: connect 0, read 345712, write 0, timeout 176
Requests/sec: 448.98
Transfer/sec: 158.37KB
```


### Logs

No error logs in nginx-gateway

Error logs in nginx

### Key Metrics

#### Containers memory

![oss-memory.png](oss-memory.png)

#### NGF Container Memory

![oss-ngf-memory.png](oss-ngf-memory.png)

### Containers CPU

![oss-cpu.png](oss-cpu.png)

### NGINX metrics

![oss-stub-status.png](oss-stub-status.png)

### Reloads

Rate of reloads - successful and errors:

![oss-reloads.png](oss-reloads.png)

Reload spikes correspond to 1 hour periods of backend re-rollouts.

No reloads finished with an error.

Reload time distribution - counts:

![oss-reload-time.png](oss-reload-time.png)


## Comparison with previous runs

Graphs look similar to 1.4.0 results.
Binary file added tests/results/longevity/1.5.0/plus-cpu.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added tests/results/longevity/1.5.0/plus-memory.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added tests/results/longevity/1.5.0/plus-ngf-memory.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added tests/results/longevity/1.5.0/plus-reloads.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added tests/results/longevity/1.5.0/plus-status.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
96 changes: 96 additions & 0 deletions tests/results/longevity/1.5.0/plus.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,96 @@
# Results

## Test environment

NGINX Plus: true

NGINX Gateway Fabric:

- Commit: 36f245bcba55935064324ff5803d66110117f7da
- Date: 2024-11-08T19:20:48Z
- Dirty: false

GKE Cluster:

- Node count: 2
- k8s version: v1.30.5-gke.1443001
- vCPUs per node: 2
- RAM per node: 4018120Ki
- Max pods per node: 110
- Zone: us-west2-a
- Instance Type: e2-medium

## Traffic

HTTP:

```text
Running 5760m test @ http://cafe.example.com/coffee
2 threads and 100 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 228.08ms 136.20ms 1.92s 63.92%
Req/Sec 232.02 153.44 1.71k 66.90%
156457702 requests in 5760.00m, 53.53GB read
Non-2xx or 3xx responses: 5
Requests/sec: 452.71
Transfer/sec: 162.41KB
```

HTTPS:

```text
Running 5760m test @ https://cafe.example.com/tea
2 threads and 100 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 229.75ms 136.23ms 1.92s 63.81%
Req/Sec 229.91 151.31 1.63k 66.59%
155060805 requests in 5760.00m, 52.19GB read
Non-2xx or 3xx responses: 3
Requests/sec: 448.67
Transfer/sec: 158.33KB
```

### Logs

No error logs in nginx-gateway

Error logs in nginx

Several errors related to R33 integration

```
2024-11-11 22:57:46.685 PST
2024/11/12 06:57:46 [crit] 49#49: open() "/var/lib/nginx/state//nginx-mgmt-state" failed (2: No such file or directory)
```


### Key Metrics

#### Containers memory

![plus-memory.png](plus-memory.png)

#### NGF Container Memory

![plus-ngf-memory.png](plus-ngf-memory.png)

### Containers CPU

![plus-cpu.png](plus-cpu.png)

### NGINX Plus metrics

![plus-status.png](plus-status.png)

### Reloads

Rate of reloads - successful and errors:

![plus-reloads.png](plus-reloads.png)

Note: compared to NGINX, we don't have as many reloads here, because NGF uses NGINX Plus API to reconfigure NGINX
for endpoints changes.

## Comparison with previous runs

Graphs look similar to 1.3.0 results.

0 comments on commit d583741

Please sign in to comment.