Verify and facilitate Google toolchain benchmark suite
The benchmark suite developed by Google consists of various open source bench items: gcstone (part of Dalvik), skia, webkit, cximage, gnugo, mpeg4 (taken from FFmpeg), and python. To compare Google and Linaro toolchain fairly, it is better to use the same self-contained environment and evaluation process by Google's toolchain benchmark suite.
However, there are some hard coded paths and improper assumption in Google's Android toolchain benchmark suite.
Blueprint information
- Status:
- Complete
- Approver:
- Alexander Sack
- Priority:
- High
- Drafter:
- Jim Huang
- Direction:
- Needs approval
- Assignee:
- Luse Cheng
- Definition:
- Pending Approval
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Jim Huang
- Completed by
- Jim Huang
Related branches
Sprints
Whiteboard
[asac Mar 19,2011]: this blueprint is in incomplete state; needs direction, drafting, proper work items so its clear what is done here and what the delivery looks like (e.g. i would think successful delivery menas integration into lava for each of them) .... seems it should be part of our validation blueprints. Work Items are in wrong syntax anyway ;). setting to high importance anyway ... as toolchain benchmark integration is what we would like to see happen asap.
[jserv Mar 19,2011]: I would like to "patch" and "re-use" the benchmark suite first since Google engineers are the only public users of this suite. The benchmark suite itself is *incomplete* for some unknown reason. Let's fix it first.
[DONE] bench: gnugo
[DONE] bench: python
[DONE] bench: skia
[DONE] bench: cximage
[DONE] bench: gcstone
[DONE] bench: mpeg4
[INVALID] bench: webkit is incomplete, and Google engineers are trying to ship new one. No need to continue hacking webkit now.
[DONE] FDO build
Work Items
Dependency tree
* Blueprints in grey have been implemented.
