Stress testing on mir

Registered by kevin gunn on 2013-05-07

Develop additional tests for mir
- operation in low memory conditions at client start & steady state
- repeated client operation over time
- rapid multiple client operation

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Mir development team
Direction:
Needs approval
Assignee:
Mir development team
Definition:
New
Series goal:
Accepted for saucy
Implementation:
Unknown
Milestone target:
milestone icon ubuntu-13.06

Related branches

Sprints

Whiteboard

- need to find or create a tool to suck up ram at programmatic intervals for mem testing
- need to create a script for controlled client operation, with repeat & programmatic # of clients (connect-disconnect, connect-render-disconnect, connect-inputevent-disconnect, etc)

May 2013 vUDS discussion
http://pad.ubuntu.com/uds-1305-client-1305-mir-thrash-testing

basic outcome - we should focus on "stress testing" first as a pilot, both for short runs (e.g. 10 min for CI of MP's) & for long ru
n (e.g. 24 hr mtbc for distro release)

May 15, 2013: kgunn
test spec for this work
https://docs.google.com/a/canonical.com/document/d/1vjjSSPLOmmgGoi5GEHk6phXJQxRgeu32E0gZc56fhf4

(?)

Work Items

Work items for ubuntu-13.05:
[kgunn] define testing requirements, data to be reported & what the disposition should be for each test: DONE
[thomir] write code for "stress" testing, e.g .multiple clients doing lots of unsynchronized stuff - separate binary package, but in the mir source tree.: DONE

Work items for ubuntu-13.08:
[thomir] make stress test part of CI: INPROGRESS
[kgunn] followup post stress test piloting to figure out OOM & mem leak testing: TODO

Dependency tree

* Blueprints in grey have been implemented.