Skip to content
Closed
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
86 changes: 86 additions & 0 deletions tests/results/dp-perf/release-2.1.2/release-2.1.2-oss.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,86 @@
# Results

## Test environment

NGINX Plus: false

NGINX Gateway Fabric:

- Commit: 8241478604f782eca497329ae47507b978d117b1
- Date: 2025-09-24T18:19:40Z
- Dirty: false

GKE Cluster:

- Node count: 15
- k8s version: v1.33.4-gke.1134000
- vCPUs per node: 2
- RAM per node: 4015668Ki
- Max pods per node: 110
- Zone: us-east1-b
- Instance Type: e2-medium

## Test1: Running latte path based routing

```text
Requests [total, rate, throughput] 30000, 1000.03, 999.97
Duration [total, attack, wait] 30.001s, 29.999s, 1.799ms
Latencies [min, mean, 50, 90, 95, 99, max] 909.791µs, 1.868ms, 1.507ms, 2.142ms, 2.756ms, 8.611ms, 60.614ms
Bytes In [total, mean] 4770000, 159.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```

## Test2: Running coffee header based routing

```text
Requests [total, rate, throughput] 30000, 1000.00, 999.95
Duration [total, attack, wait] 30.002s, 30s, 1.712ms
Latencies [min, mean, 50, 90, 95, 99, max] 991.792µs, 2.102ms, 1.659ms, 2.466ms, 3.321ms, 11.629ms, 73.799ms
Bytes In [total, mean] 4800000, 160.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```

## Test3: Running coffee query based routing

```text
Requests [total, rate, throughput] 30000, 1000.04, 999.98
Duration [total, attack, wait] 30.001s, 29.999s, 1.599ms
Latencies [min, mean, 50, 90, 95, 99, max] 964.301µs, 2.088ms, 1.589ms, 2.194ms, 2.891ms, 12.188ms, 77.709ms
Bytes In [total, mean] 5040000, 168.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```

## Test4: Running tea GET method based routing

```text
Requests [total, rate, throughput] 30000, 1000.01, 999.96
Duration [total, attack, wait] 30.001s, 30s, 1.373ms
Latencies [min, mean, 50, 90, 95, 99, max] 935.247µs, 1.88ms, 1.503ms, 2.006ms, 2.429ms, 11.029ms, 73.867ms
Bytes In [total, mean] 4710000, 157.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```

## Test5: Running tea POST method based routing

```text
Requests [total, rate, throughput] 30000, 1000.01, 999.97
Duration [total, attack, wait] 30.001s, 30s, 1.329ms
Latencies [min, mean, 50, 90, 95, 99, max] 981.259µs, 1.759ms, 1.535ms, 1.991ms, 2.43ms, 7.522ms, 29.702ms
Bytes In [total, mean] 4710000, 157.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```
86 changes: 86 additions & 0 deletions tests/results/dp-perf/release-2.1.2/release-2.1.2-plus.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,86 @@
# Results

## Test environment

NGINX Plus: true

NGINX Gateway Fabric:

- Commit: 8241478604f782eca497329ae47507b978d117b1
- Date: 2025-09-25T01:19:35Z
- Dirty: false

GKE Cluster:

- Node count: 15
- k8s version: v1.33.4-gke.1134000
- vCPUs per node: 2
- RAM per node: 4015672Ki
- Max pods per node: 110
- Zone: us-south1-a
- Instance Type: e2-medium

## Test1: Running latte path based routing

```text
Requests [total, rate, throughput] 30000, 1000.04, 1000.01
Duration [total, attack, wait] 30s, 29.999s, 899.747µs
Latencies [min, mean, 50, 90, 95, 99, max] 755.39µs, 1.083ms, 972.127µs, 1.139ms, 1.257ms, 3.409ms, 34.066ms
Bytes In [total, mean] 4830000, 161.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```

## Test2: Running coffee header based routing

```text
Requests [total, rate, throughput] 30000, 1000.04, 1000.01
Duration [total, attack, wait] 30s, 29.999s, 960.429µs
Latencies [min, mean, 50, 90, 95, 99, max] 790.502µs, 1.086ms, 1.017ms, 1.192ms, 1.293ms, 2.776ms, 13.993ms
Bytes In [total, mean] 4860000, 162.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```

## Test3: Running coffee query based routing

```text
Requests [total, rate, throughput] 30000, 1000.00, 999.97
Duration [total, attack, wait] 30.001s, 30s, 956.779µs
Latencies [min, mean, 50, 90, 95, 99, max] 807.149µs, 1.174ms, 1.02ms, 1.204ms, 1.338ms, 4.79ms, 37.843ms
Bytes In [total, mean] 5100000, 170.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```

## Test4: Running tea GET method based routing

```text
Requests [total, rate, throughput] 30000, 1000.04, 1000.00
Duration [total, attack, wait] 30s, 29.999s, 1.032ms
Latencies [min, mean, 50, 90, 95, 99, max] 773.587µs, 1.065ms, 1.006ms, 1.176ms, 1.264ms, 2.48ms, 20.731ms
Bytes In [total, mean] 4770000, 159.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```

## Test5: Running tea POST method based routing

```text
Requests [total, rate, throughput] 30000, 1000.00, 999.97
Duration [total, attack, wait] 30.001s, 30s, 937.91µs
Latencies [min, mean, 50, 90, 95, 99, max] 805.184µs, 1.194ms, 1.011ms, 1.191ms, 1.312ms, 4.171ms, 58.715ms
Bytes In [total, mean] 4770000, 159.00
Bytes Out [total, mean] 0, 0.00
Success [ratio] 100.00%
Status Codes [code:count] 200:30000
Error Set:
```
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.
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.
53 changes: 53 additions & 0 deletions tests/results/ngf-upgrade/release-2.1.2/release-2.1.2-oss.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
# Results

## Test environment

NGINX Plus: false

NGINX Gateway Fabric:

- Commit: 8241478604f782eca497329ae47507b978d117b1
- Date: 2025-09-24T18:19:40Z
- Dirty: false

GKE Cluster:

- Node count: 15
- k8s version: v1.33.4-gke.1134000
- vCPUs per node: 2
- RAM per node: 4015668Ki
- Max pods per node: 110
- Zone: us-east1-b
- Instance Type: e2-medium

## Test: Send https /tea traffic

```text
Requests [total, rate, throughput] 6000, 100.01, 99.66
Duration [total, attack, wait] 59.994s, 59.993s, 1.742ms
Latencies [min, mean, 50, 90, 95, 99, max] 579.788µs, 236.428ms, 1.95ms, 12.814ms, 2.333s, 4.553s, 5.076s
Bytes In [total, mean] 928726, 154.79
Bytes Out [total, mean] 0, 0.00
Success [ratio] 99.65%
Status Codes [code:count] 0:21 200:5979
Error Set:
Get "https://cafe.example.com/tea": dial tcp 0.0.0.0:0->10.142.0.59:443: connect: connection refused
```

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

## Test: Send http /coffee traffic

```text
Requests [total, rate, throughput] 6000, 100.01, 99.64
Duration [total, attack, wait] 59.994s, 59.992s, 1.987ms
Latencies [min, mean, 50, 90, 95, 99, max] 591.987µs, 232.293ms, 1.892ms, 12.183ms, 2.28s, 4.543s, 5.056s
Bytes In [total, mean] 962458, 160.41
Bytes Out [total, mean] 0, 0.00
Success [ratio] 99.63%
Status Codes [code:count] 0:22 200:5978
Error Set:
Get "http://cafe.example.com/coffee": dial tcp 0.0.0.0:0->10.142.0.59:80: connect: connection refused
```

![http-oss.png](http-oss.png)
57 changes: 57 additions & 0 deletions tests/results/ngf-upgrade/release-2.1.2/release-2.1.2-plus.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
# Results

## Test environment

NGINX Plus: true

NGINX Gateway Fabric:

- Commit: 8241478604f782eca497329ae47507b978d117b1
- Date: 2025-09-25T01:19:35Z
- Dirty: false

GKE Cluster:

- Node count: 15
- k8s version: v1.33.4-gke.1134000
- vCPUs per node: 2
- RAM per node: 4015672Ki
- Max pods per node: 110
- Zone: us-south1-a
- Instance Type: e2-medium

## Test: Send https /tea traffic

```text
Requests [total, rate, throughput] 6000, 100.01, 99.61
Duration [total, attack, wait] 59.994s, 59.992s, 2.553ms
Latencies [min, mean, 50, 90, 95, 99, max] 501.4µs, 629.899ms, 1.546ms, 2.856s, 5.518s, 7.81s, 8.341s
Bytes In [total, mean] 928271, 154.71
Bytes Out [total, mean] 0, 0.00
Success [ratio] 99.60%
Status Codes [code:count] 0:24 200:5976
Error Set:
Get "https://cafe.example.com/tea": read tcp 10.206.0.17:60039->10.206.0.24:443: read: connection reset by peer
Get "https://cafe.example.com/tea": write tcp 10.206.0.17:44027->10.206.0.24:443: write: connection reset by peer
Get "https://cafe.example.com/tea": dial tcp 0.0.0.0:0->10.206.0.24:443: connect: connection refused
Copy link
Collaborator

Choose a reason for hiding this comment

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

A few connection errors during the upgrade process.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I know you were worried about these

Copy link
Contributor Author

@salonichf5 salonichf5 Sep 25, 2025

Choose a reason for hiding this comment

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

should we create a story to track this? debugging now would definitely take long but could also lead to more community bugs and issue if it is an actual issue during upgrade

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think let's wait for another automated NFR run on main to see if it's still an issue. I don't think it's a blocker for now.

```

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

## Test: Send http /coffee traffic

```text
Requests [total, rate, throughput] 6000, 100.01, 99.61
Duration [total, attack, wait] 59.994s, 59.992s, 2.318ms
Latencies [min, mean, 50, 90, 95, 99, max] 492.213µs, 611.258ms, 1.381ms, 2.64s, 5.498s, 7.789s, 8.344s
Bytes In [total, mean] 962095, 160.35
Bytes Out [total, mean] 0, 0.00
Success [ratio] 99.60%
Status Codes [code:count] 0:24 200:5976
Error Set:
Get "http://cafe.example.com/coffee": read tcp 10.206.0.17:42805->10.206.0.24:80: read: connection reset by peer
Get "http://cafe.example.com/coffee": read tcp 10.206.0.17:46097->10.206.0.24:80: read: connection reset by peer
Get "http://cafe.example.com/coffee": dial tcp 0.0.0.0:0->10.206.0.24:80: connect: connection refused
```

![http-plus.png](http-plus.png)
111 changes: 111 additions & 0 deletions tests/results/reconfig/release-2.1.2/release-2.1.2-oss.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,111 @@
# Results

## Test environment

NGINX Plus: false

NGINX Gateway Fabric:

- Commit: 8241478604f782eca497329ae47507b978d117b1
- Date: 2025-09-24T18:19:40Z
- Dirty: false

GKE Cluster:

- Node count: 15
- k8s version: v1.33.4-gke.1134000
- vCPUs per node: 2
- RAM per node: 4015668Ki
- Max pods per node: 110
- Zone: us-east1-b
- Instance Type: e2-medium

## Test 1: Resources exist before startup - NumResources 30

### Time to Ready

Time To Ready Description: From when NGF starts to when the NGINX configuration is fully configured
- TimeToReadyTotal: 23s

### Event Batch Processing

- Event Batch Total: 10
- Event Batch Processing Average Time: 12ms
- Event Batch Processing distribution:
- 500.0ms: 10
- 1000.0ms: 10
- 5000.0ms: 10
- 10000.0ms: 10
- 30000.0ms: 10
- +Infms: 10

### NGINX Error Logs

## Test 1: Resources exist before startup - NumResources 150

### Time to Ready

Time To Ready Description: From when NGF starts to when the NGINX configuration is fully configured
- TimeToReadyTotal: 25s

### Event Batch Processing

- Event Batch Total: 9
- Event Batch Processing Average Time: 37ms
- Event Batch Processing distribution:
- 500.0ms: 9
- 1000.0ms: 9
- 5000.0ms: 9
- 10000.0ms: 9
- 30000.0ms: 9
- +Infms: 9

### NGINX Error Logs

## Test 2: Start NGF, deploy Gateway, wait until NGINX agent instance connects to NGF, create many resources attached to GW - NumResources 30

### Time to Ready

Time To Ready Description: From when NGINX receives the first configuration created by NGF to when the NGINX configuration is fully configured
- TimeToReadyTotal: 24s

### Event Batch Processing

- Event Batch Total: 272
- Event Batch Processing Average Time: 28ms
- Event Batch Processing distribution:
- 500.0ms: 266
- 1000.0ms: 272
- 5000.0ms: 272
- 10000.0ms: 272
- 30000.0ms: 272
- +Infms: 272

### NGINX Error Logs
2025/09/25 03:10:51 [emerg] 8#8: unexpected end of file, expecting "}" in /etc/nginx/conf.d/http.conf:459
2025/09/25 03:10:56 [emerg] 8#8: unexpected end of file, expecting "}" in /etc/nginx/conf.d/http.conf:2433

## Test 2: Start NGF, deploy Gateway, wait until NGINX agent instance connects to NGF, create many resources attached to GW - NumResources 150

### Time to Ready

Time To Ready Description: From when NGINX receives the first configuration created by NGF to when the NGINX configuration is fully configured
- TimeToReadyTotal: 123s

### Event Batch Processing

- Event Batch Total: 1315
- Event Batch Processing Average Time: 23ms
- Event Batch Processing distribution:
- 500.0ms: 1277
- 1000.0ms: 1314
- 5000.0ms: 1315
- 10000.0ms: 1315
- 30000.0ms: 1315
- +Infms: 1315

### NGINX Error Logs
2025/09/25 03:15:10 [emerg] 8#8: unexpected end of file, expecting "}" in /etc/nginx/conf.d/http.conf:1466
2025/09/25 03:15:14 [emerg] 8#8: unexpected end of file, expecting ";" or "}" in /etc/nginx/conf.d/http.conf:3065
2025/09/25 03:15:15 [emerg] 8#8: unexpected end of file, expecting "}" in /etc/nginx/conf.d/http.conf:3560
2025/09/25 03:15:23 [emerg] 8#8: directive "upstream" has no opening "{" in /etc/nginx/conf.d/http.conf:7773
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hm, we're seeing these again.

Copy link
Contributor Author

@salonichf5 salonichf5 Sep 25, 2025

Choose a reason for hiding this comment

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

yeah just what I was discussing with Ciara but this is a different issue than the agent bug

Loading
Loading