Closed adambollen closed 1 month ago
Generated on: | 10/03/2024 - 20:44 | ||
Description | Previous | Current | Delta |
Coverage date: | 10/03/2024 - 20:43 | 10/03/2024 - 20:44 | |
Tag: | main | d310944 | |
Line coverage: | 81.5% | 81.5% | 0.0% |
Covered lines: | 3234 | 3234 | 0 |
Coverable lines: | 3967 | 3967 | 0 |
Total lines: | 14858 | 14858 | 0 |
Branch coverage: | 70.3% | 70.3% | 0.0% |
Covered branches: | 1049 | 1049 | 0 |
Total branches: | 1492 | 1492 | 0 |
Method coverage: | Feature is only available for sponsors |
Description
When a perf test is going to paginate, it will now paginate via three different methods: using
client.QueryAsync()
with theafter
token; usingPaginateAsync()
; and usingFlattenAsync()
. Also, when reporting metrics on the overhead, it will now divide by the number of queries observed in theStatsCollector
to make comparing the various query perf numbers clearer.Motivation and context
How was the change tested?
Ran it a number of times locally; the new output will automatically be picked up and sent to #alerts-driver-perf in Slack.
Screenshots (if appropriate):
Change types
Checklist:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.