Development Benchmarking

Registered by Mounir Bsaibes on 2011-12-14

We currently use merge requests to review patches and check them for
correctness. We now have enough builder capacity to also benchmark
with each commit to also check for regressions.

Discuss:
 * Extra capacity required, if any
 * How to compare the results across runs
 * How to check the variation across boards
 * How to check for any unexpected variation
 * How to log the results
 * Any licensing issues and what we can show publicly

Blueprint information

Status:
Not started
Approver:
Michael Hope
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Asa Sandahl
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.