search

kubermatic / kubecarrier

KubeCarrier - Service Management at Scale
Apache License 2.0
297 stars 14 forks source link

increased APIServer limits #511

Closed nmiculinic closed 4 years ago

nmiculinic commented 4 years ago

On my machine API server took on average 1000-2000ms to respond to every API request. A bit too much, isn't it? 

NONE
kubermatic-bot commented 4 years ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nmiculinic

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/kubermatic/kubecarrier/blob/master/OWNERS)~~ [nmiculinic] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
aborilov commented 4 years ago 
Running 10s test @ https://localhost:9443/v1/whoami
  6 threads and 10 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   113.27ms   93.53ms 494.39ms   63.38%
    Req/Sec    10.21      6.45    30.00     70.79%
  529 requests in 10.09s, 174.61KB read
Requests/sec:     52.41
Transfer/sec:     17.30KB

on my machine it takes only 113ms avg

nmiculinic commented 4 years ago

/retest

hmmmm....yeah, I kinda feel I'm overusing my laptop with 2 kind clusters ,slack, firefox, InteliJ... The memory gets full and I'm swapping :-/

jiachengxu commented 4 years ago 
Running 10s test @ https://localhost:9443/v1/whoami
  6 threads and 10 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   113.27ms   93.53ms 494.39ms   63.38%
    Req/Sec    10.21      6.45    30.00     70.79%
  529 requests in 10.09s, 174.61KB read
Requests/sec:     52.41
Transfer/sec:     17.30KB

on my machine it takes only 113ms avg

@aborilov , which tool did you use for testing? I would like also to have a try :)

aborilov commented 4 years ago 
Running 10s test @ https://localhost:9443/v1/whoami
  6 threads and 10 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   113.27ms   93.53ms 494.39ms   63.38%
    Req/Sec    10.21      6.45    30.00     70.79%
  529 requests in 10.09s, 174.61KB read
Requests/sec:     52.41
Transfer/sec:     17.30KB

on my machine it takes only 113ms avg

@aborilov , which tool did you use for testing? I would like also to have a try :)

https://github.com/wg/wrk wrk -t 6 -c 10 https://localhost:9443/v1/whoami

nmiculinic commented 4 years ago

What about API endpoint doing more work? 100ms....it's actually a lot for endpoint doing pretty much nothing.

aborilov commented 4 years ago

What about API endpoint doing more work? 100ms....it's actually a lot for endpoint doing pretty much nothing.

we need to do such tests on real k8s cluster, not kind with kubeproxy.

aborilov commented 4 years ago

and yeah, 100ms too much for doing nothing

jiachengxu commented 4 years ago

/lgtm

kubermatic-bot commented 4 years ago

LGTM label has been added.

Git tree hash: 54762bca3860dcdbcbbd101cb501295f97ddee70

kubermatic-triage-bot commented 4 years ago

/retest This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

Also, here is a cat. /meow

kubermatic-bot commented 4 years ago

@kubermatic-triage-bot: cat image

In response to [this](https://github.com/kubermatic/kubecarrier/pull/511#issuecomment-662532906): >/retest >This bot automatically retries jobs that failed/flaked on approved PRs > >Review the [full test history](https://prow.loodse.com/pr-history/?org=kubermatic&repo=kubecarrier&pr=511) > >Silence the bot with an `/lgtm cancel` or `/hold` comment for consistent failures. > >Also, here is a cat. >/meow Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
kubermatic-triage-bot commented 4 years ago

/retest This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

Also, here is a cat. /meow

kubermatic-bot commented 4 years ago

@kubermatic-triage-bot: cat image

In response to [this](https://github.com/kubermatic/kubecarrier/pull/511#issuecomment-662577907): >/retest >This bot automatically retries jobs that failed/flaked on approved PRs > >Review the [full test history](https://prow.loodse.com/pr-history/?org=kubermatic&repo=kubecarrier&pr=511) > >Silence the bot with an `/lgtm cancel` or `/hold` comment for consistent failures. > >Also, here is a cat. >/meow Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.