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

Have performance issue if Cloud CDN is enabled #1469

Closed
WLun001 opened this issue Jun 9, 2021 · 2 comments
Closed

Have performance issue if Cloud CDN is enabled #1469

WLun001 opened this issue Jun 9, 2021 · 2 comments

Comments

@WLun001
Copy link

WLun001 commented Jun 9, 2021

I found out that GKE Ingress (with Cloud CDN) is way slower than GKE Ingress (without Cloud CDN), when testing against hello-world API server written in Go, (wait for 200ms and return response). Here is the benchmark results, access through public IP address, no DNS, no HTTPS, not cacheable by CDN and no server-side caching.

Tested enabled Cloud CDN from backend config CRD or from Cloud console, workload were running on GKE autopilot

With Cloud CDN

$ bombardier -c 200 -n 100000 IP_ADDRESS

Bombarding IP_ADDRESS with 100000 request(s) using 200 connection(s)
 100000 / 100000 [=====] 100.00% 197/s 8m25s
Done!
Statistics        Avg      Stdev        Max
  Reqs/sec       206.84     622.51    7707.32
  Latency         1.01s   410.20ms      5.48s
  HTTP codes:
    1xx - 0, 2xx - 100000, 3xx - 0, 4xx - 0, 5xx - 0
    others - 0
  Throughput:    52.75KB/s

Without Cloud CDN

$ bombardier -c 200 -n 100000 IP_ADDRESS

Bombarding IP_ADDRESS with 100000 request(s) using 200 connection(s)
 100000 / 100000 [=====] 100.00% 885/s 1m52s
Done!
Statistics        Avg      Stdev        Max
  Reqs/sec       899.61     760.42   10838.69
  Latency      225.16ms    17.68ms   533.07ms
  HTTP codes:
    1xx - 0, 2xx - 100000, 3xx - 0, 4xx - 0, 5xx - 0
    others - 0
  Throughput:   197.52KB/s

with service type Load Balancer

$ bombardier -c 200 -n 100000 IP_ADDRESS

 Bombarding IP_ADDRESS/ with 100000 request(s) using 200 connection(s)
 100000 / 100000 [=====] 100.00% 911/s 1m49s
Done!
Statistics        Avg      Stdev        Max
  Reqs/sec       922.00     827.36    5866.92
  Latency      218.86ms     9.84ms   369.95ms
  HTTP codes:
    1xx - 0, 2xx - 100000, 3xx - 0, 4xx - 0, 5xx - 0
    others - 0
  Throughput:   191.66KB/s

@swetharepakula
Copy link
Member

Thanks for reporting the issue! The ingress-gce repository only has the controller code that is used to configure the loadbalancer. Since the performance issue seems is with the load balancer and not the controller, please open a support ticket with GCP with this info and cluster details.

@Olegt0rr
Copy link

@WLun001, since the article points here, please post any news about this issue here or update an article

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants