Skip to content
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

v1.1.0 Dataplane performance #1349

Merged
merged 1 commit into from
Dec 8, 2023
Merged
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
123 changes: 123 additions & 0 deletions tests/dataplane-performance/results/1.1.0/1.1.0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,123 @@
# Results

## Test environment

GKE cluster:

- Node count: 3
- Instance Type: e2-medium
- k8s version: 1.27.3-gke.100
- Zone: europe-west2-b
- Total vCPUs: 6
- Total RAM: 12GB
- Max pods per node: 110

Test VM:

- Instance Type: e2-medium
- Zone: europe-west2-b
- vCPUS: 2
- RAM: 4GB

NGF deployment:

- NGF version: edge - git commit 21a2507d3d25ac0428384dce2c042799ed28b856
- NGINX Version: 1.25.3

## Summary

- Path based routing performance has decreased slightly since 1.0.0
sjberman marked this conversation as resolved.
Show resolved Hide resolved
- Header based routing performance has increased significantly since 1.0.0
- Query based routing performance has slightly increased since 1.0.0
- Method based routing on average between GET and POST based has remained roughly the same as v1.0.0, but in this run
the performance of the POST method was significantly less than that of the GET method

## Test1: Running latte path based routing

```console
Running 30s test @ http://cafe.example.com/latte
2 threads and 10 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 5.90ms 5.95ms 93.07ms 91.58%
Req/Sec 1.02k 229.69 1.92k 75.67%
Latency Distribution
50% 4.35ms
75% 6.50ms
90% 10.73ms
99% 32.50ms
60729 requests in 30.02s, 21.66MB read
Requests/sec: 2023.13
Transfer/sec: 738.91KB
```

## Test2: Running coffee header based routing

```console
Running 30s test @ http://cafe.example.com/coffee
2 threads and 10 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 6.83ms 7.92ms 136.86ms 93.66%
Req/Sec 0.89k 274.77 1.68k 68.00%
Latency Distribution
50% 4.98ms
75% 7.56ms
90% 11.89ms
99% 44.04ms
53421 requests in 30.01s, 19.10MB read
Requests/sec: 1779.97
Transfer/sec: 651.84KB
```

## Test3: Running coffee query based routing

```console
Running 30s test @ http://cafe.example.com/coffee?TEST=v2
2 threads and 10 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 6.84ms 7.76ms 129.66ms 93.62%
Req/Sec 0.88k 206.19 1.58k 77.67%
Latency Distribution
50% 4.83ms
75% 7.63ms
90% 11.87ms
99% 41.39ms
52846 requests in 30.01s, 19.30MB read
Requests/sec: 1760.75
Transfer/sec: 658.55KB
```

## Test4: Running tea GET method based routing

```console
Running 30s test @ http://cafe.example.com/tea
2 threads and 10 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 6.55ms 6.41ms 97.49ms 91.74%
Req/Sec 0.90k 190.25 1.64k 77.17%
Latency Distribution
50% 4.85ms
75% 7.55ms
90% 11.80ms
99% 35.33ms
53661 requests in 30.02s, 19.04MB read
Requests/sec: 1787.34
Transfer/sec: 649.30KB
```

## Test5: Running tea POST method based routing

```console
Running 30s test @ http://cafe.example.com/tea
2 threads and 10 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 31.45ms 43.10ms 408.63ms 81.26%
Req/Sec 458.81 332.92 1.73k 61.26%
Latency Distribution
50% 6.70ms
75% 51.43ms
90% 107.48ms
99% 146.54ms
26914 requests in 30.03s, 9.55MB read
Requests/sec: 896.12
Transfer/sec: 325.54KB
```
Loading