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

[test/performance] round computed rate in real-traffic-test #15641

Conversation

maschmid
Copy link
Contributor

real-traffic-test benchmark SLA 2 fails frequently just because the computed rate is not exactly the expected value , e.g. https://prow.knative.dev/view/gs/knative-prow/logs/performance-tests_serving_main_periodic/1862287597506662400

SLA 2 failed. vegeta rate is 2000.006921, expected Rate is 2000.000000

Let's do the same here as we already to in https://github.com/knative/serving/blob/main/test/performance/benchmarks/rollout-probe/main.go#L234 , and add tolerance to the rate comparison to fit within the nearest integer.

  • round computed Rate on real-traffic-test benchmark

@knative-prow knative-prow bot requested review from izabelacg and skonto November 29, 2024 17:52
@knative-prow knative-prow bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 29, 2024
@maschmid maschmid changed the title round computed rate in real-traffic-test [test/performance] round computed rate in real-traffic-test Nov 29, 2024
Copy link

codecov bot commented Nov 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.53%. Comparing base (5717d19) to head (8eed01e).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #15641   +/-   ##
=======================================
  Coverage   83.53%   83.53%           
=======================================
  Files         219      219           
  Lines       17427    17427           
=======================================
  Hits        14558    14558           
+ Misses       2498     2496    -2     
- Partials      371      373    +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@skonto
Copy link
Contributor

skonto commented Dec 9, 2024

/test ?

Copy link

knative-prow bot commented Dec 9, 2024

@skonto: The following commands are available to trigger required jobs:

/test build-tests
/test contour-latest
/test contour-tls
/test gateway-api-latest
/test istio-latest-no-mesh
/test istio-latest-no-mesh-tls
/test kourier-stable
/test kourier-stable-tls
/test unit-tests
/test upgrade-tests

The following commands are available to trigger optional jobs:

/test gateway-api-latest-and-contour
/test https
/test istio-latest-mesh
/test istio-latest-mesh-short
/test istio-latest-mesh-tls
/test performance-tests

Use /test all to run the following jobs that were automatically triggered:

build-tests_serving_main
istio-latest-no-mesh-tls_serving_main
istio-latest-no-mesh_serving_main
unit-tests_serving_main
upgrade-tests_serving_main

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@skonto
Copy link
Contributor

skonto commented Dec 9, 2024

/test performance-tests

@skonto
Copy link
Contributor

skonto commented Dec 13, 2024

Din't pass the first SLA. :(

2024/12/09 08:57:07 Starting vegeta attack for with 2000 RPS for duration: 5m0s
2024/12/09 08:57:23 error occurred calling target. Err: unexpected EOF, url: http://perftest-17-hzoafmoh.default.svc.cluster.local?sleep=4793, method: POST
Requests      [total, rate, throughput]         599996, 1999.86, 1999.83
Duration      [total, attack, wait]             5m0s, 5m0s, 5.391ms
Latencies     [min, mean, 50, 90, 95, 99, max]  3.354ms, 7.654ms, 5.401ms, 9.567ms, 14.572ms, 34.819ms, 1.012s
Bytes In      [total, mean]                     7341775345, 12236.37
Bytes Out     [total, mean]                     17131476748, 28552.65
Success       [ratio]                           100.00%
2024/12/09 09:02:07 Cleaning up all created services
Status Codes  [code:count]                      0:1  200:599995  
Error Set:
unexpected EOF
2024/12/09 09:02:10 Shutting down InfluxReporter
2024/12/09 09:02:10 SLA 1 failed. Errors occurred: 1
job.batch "real-traffic-test" deleted

@skonto
Copy link
Contributor

skonto commented Dec 13, 2024

/test performance-tests

@skonto
Copy link
Contributor

skonto commented Dec 13, 2024

/lgtm
/hold for the tests

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 13, 2024
@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Dec 13, 2024
@skonto
Copy link
Contributor

skonto commented Dec 13, 2024

/approve

Copy link

knative-prow bot commented Dec 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maschmid, skonto

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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 13, 2024
@skonto
Copy link
Contributor

skonto commented Dec 16, 2024

@maschmid hi, this still fails:

2024/12/13 09:17:27 Cleaning up all created services
2024/12/13 09:17:29 Shutting down InfluxReporter
2024/12/13 09:17:29 SLA 1 failed. Errors occurred: 1

Not sure if we can verify it here. Could you take a look on this one too? Btw I will stamp it based on the other test.

@maschmid
Copy link
Contributor Author

Trying to see if #15654 helps with the SLA 1

@maschmid maschmid closed this Dec 17, 2024
@maschmid
Copy link
Contributor Author

included in #15654

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants