Skip to content

Add 2.0 longevity results #3429

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

Merged
merged 1 commit into from
Jun 2, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added tests/results/longevity/2.0.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/2.0.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.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
43 changes: 43 additions & 0 deletions tests/results/longevity/2.0.0/oss.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# Results

## Summary

These results are incomplete and may be inaccurate. The test was stopped manually about 1 day early, and results such as logs and traffic summary were not collected properly by the teardown scripts/functions.

There are fewer dashboards to collect now after the change in architecture, as we don't have the same metrics as we did before, mainly relating to reloads.

One thing of note is the significant increase in memory usage for the NGF control plane container. For our NGINX Plus run, the opposite occurred, where the NGINX container had high memory.

## Test environment

NGINX Plus: false

NGINX Gateway Fabric:

- Commit: cc3c907ff668d886cac719df2d77b685370ad5f8
- Date: 2025-05-30T18:25:58Z
- Dirty: false

GKE Cluster:

- Node count: 3
- k8s version: v1.32.4-gke.1106006
- vCPUs per node: 2
- RAM per node: 4015484Ki
- Max pods per node: 110
- Zone: us-west2-a
- Instance Type: e2-medium

## 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)
Binary file added tests/results/longevity/2.0.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/2.0.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.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
65 changes: 65 additions & 0 deletions tests/results/longevity/2.0.0/plus.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
# Results

## Summary

These results are incomplete and may be inaccurate. The test was stopped manually about 1 day early, and results such as logs and traffic summary were not collected properly by the teardown scripts/functions.

There are fewer dashboards to collect now after the change in architecture, as we don't have the same metrics as we did before, mainly relating to reloads.

One thing of note is the significant increase in memory usage for the NGINX container.

## Test environment

NGINX Plus: true

NGINX Gateway Fabric:

- Commit: cc3c907ff668d886cac719df2d77b685370ad5f8
- Date: 2025-05-30T18:25:58Z
- Dirty: false

GKE Cluster:

- Node count: 3
- k8s version: v1.32.4-gke.1106006
- vCPUs per node: 2
- RAM per node: 4015484Ki
- Max pods per node: 110
- Zone: us-west2-a
- Instance Type: e2-medium

## Traffic

HTTP:

```text
```

HTTPS:

```text
```


## Error Logs

### nginx-gateway



### nginx
2025/06/01 15:34:12 [error] 78#78: *157671523 no live upstreams while connecting to upstream, client: 35.236.69.111, server: cafe.example.com, request: "GET /tea HTTP/1.1", upstream: "http://longevity_tea_80/tea", host: "cafe.example.com"

## 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)
Loading