| Summary: | Benchmark meta-intel build VS generic-x86* build in OE | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Jianxun Zhang <jianxun.zhang> |
| Component: | bsps-meta-intel | Assignee: | Todor Minchev <todor.minchev> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | brian.avery, sgw |
| Version: | 2.2 | ||
| Target Milestone: | 2.3 M2 | ||
| Hardware: | MinnowBoard Max | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Jianxun Zhang
2016-10-25 21:04:12 UTC
So far I have made some progress: () figured out how to build PTS in the poky image. PTS recipes are not in poky by default. They are hosted in meta-oe in meta-openembedded project. () Enable network connection on target so the built PTS can download tests and suites. Not all the proxy servers in my site work for PTS. I have found one can work, anyway. (I am using a NUC4 for prototype) But there are more findings and work I want to mention: Individual PTS test depends on other upstream projects. And it will try to download these projects and even compile them during the installation of the test. The pulled upstream project is not necessary the same version that built in poky image. At least for a graphic test, as an example, cairo-perf-trace test is hardcoded to pull an older version of cairo 1.10.2 then poky, compile perf tool in cairo, generates a script to run the perf-tool in PTS. https://openbenchmarking.org/innhold/bc5996298885f1d19395ef55bb2251ce002c1088 (I tried other several tests on sato image but haven't seen any of them can be installed out of box.) That means the result from PTS test won't reflect the actual performance poky build flashed on a board. And figuring how to make each test based on components in poky won't be easy. To try to follow PTS procedure, I will give core-image-lsb-dev image a try to see if PTS can go through the installation of selected tests. However, It will need to download and build packages at run time on target. I guess this will take a very lone time on a Minnow Max board. Another consideration is the required size of storage. I have seen some tests claims several hundred MB in installation. Maybe we need to connect a SSD drive to Minnnowmax beside from other runtime overhead I have mentioned. I ran a few Phoronix benchmarks(disk IO, memory, CPU and overall system performance) which compare i7-64 and genericx86-64. These are reasonably small in size and independent of the packages installed in core-image-sato. The next step will be to have these deployed and run automatically in the runtime lab. That will be good if PTS can run some cases against the packages in image flashed on target. But you could need to pick up test cases carefully not to introduce cases requiring download and compiling if there is no a generic way to do so in PTS. This is completed, however the Phoronix cache server is very flaky and needs to be restarted periodically. I have opened another bug to track this. https://bugzilla.yoctoproject.org/show_bug.cgi?id=11046 |