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

Properly document cloud aggregation options #194

Closed
na-- opened this issue May 17, 2018 · 0 comments · Fixed by #386
Closed

Properly document cloud aggregation options #194

na-- opened this issue May 17, 2018 · 0 comments · Fixed by #386
Labels
Area: OSS Content Improvements or additions to community/oss documentation Priority: Low

Comments

@na--
Copy link
Member

na-- commented May 17, 2018

The only current documentation about the aggregation algorithm and options resides here. It has to be expanded with better descriptions, rationale and examples in it's own section of the k6 docs.

@na-- na-- self-assigned this May 17, 2018
na-- referenced this issue in grafana/k6 Aug 16, 2018
Now buckets with fewer HTTP samples can also be aggregated, with outlier detection using the original sorting method, but with interpolation for improved accruacy. This is a more resource-intensive process, so for larger sample sizes quickselect is still the preferred algorithm.

There's also a new AggregationSkipOutlierDetection option that disables outlier detection altogether. It is disabled by default and is intended mostly for testing purposes.

And finally, the in-code documentation about the aggregation algorithm and options is expanded, which should help with https://github.com/loadimpact/k6/issues/628 and #743
@na-- na-- transferred this issue from grafana/k6 Jan 21, 2021
@na-- na-- removed their assignment Jan 21, 2021
@na-- na-- added Area: OSS Content Improvements or additions to community/oss documentation Priority: Low Status: Available labels Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: OSS Content Improvements or additions to community/oss documentation Priority: Low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant