Investigate Android Benchmark Variance
Registered by
Zach Pfeffer
Why?
The Toolchain Working Group has requested that we create a system where the run-to-run variance of our benchmarks is 1% for native and JAVA workloads. These low -variances will allow comparisons across baselines and allow benchmark guided optimization. An effort t olower this variance was done and the feedback from the TCWG was to look at the higher variances and see what's causing them.
Context?
This is part of the larger ARM benchmarking effort.
What gets produced?
A mechanism that runs before a benchmark that puts the system into a lower variance state han it was or a list of benchmarks who's variances cannot be characterized or lowered.
Where will the work get put?
A script on android.
Blueprint information
- Status:
- Not started
- Approver:
- Zach Pfeffer
- Priority:
- Undefined
- Drafter:
- vishal
- Direction:
- Needs approval
- Assignee:
- vishal
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)