Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

metrics: evaluate and reduce 'noise' in metrics tests #879

Open
grahamwhaley opened this issue Feb 2, 2018 · 0 comments
Open

metrics: evaluate and reduce 'noise' in metrics tests #879

grahamwhaley opened this issue Feb 2, 2018 · 0 comments

Comments

@grahamwhaley
Copy link
Contributor

Some of our tests are quite 'noisy' in their results. That makes then tricky to use for CI.
Evaluate the noise in the tests, particularly the tests we use in the CI.
Evaluate (starting with the noisiest first maybe) where the noise comes from, and what, if anything, we can do to mitigate it.

Random notes:

  • network and storage tests tend to be noisy - in some ways that is the nature of the beast for those.
  • running the tests multiple times and aggregating reduces noise, but can take a substantial time
  • there are a number of things we can contemplate to reduce noise, including
    • better use of the tests (investigate the available test program arguments for instance)
    • pinning to CPUs - inside and outside the container
    • pinning power save states on the host
    • smarter use of the test results (some tests generate quartiles etc., and we presently ignore them)
mcastelino pushed a commit to mcastelino/tests that referenced this issue Jan 23, 2019
Since the new feature: memory hotplug, which uses the " (qemu)
device_add pc-dimm,id=dimm1,memdev=mem1 " to limit memory on runtime,
is not availble on arm platform, for now we just have to resort to
skip relevant tests in aarch64.

Fixes: clearcontainers#879

Signed-off-by: Penny Zheng penny.zheng@arm.com
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant