| Summary: | build-perf-test: Add test to verify if parsing time is improved with a hot codeparser cache | ||
|---|---|---|---|
| Product: | [QA/Testing] Build Testing | Reporter: | Jose Perez C <jose.perez.carranza> |
| Component: | general | Assignee: | Markus Lehtonen <markus.lehtonen> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | markus.lehtonen |
| Version: | 2.3 | ||
| Target Milestone: | 2.3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Jose Perez C
2016-11-30 14:01:09 UTC
Measuring the improvement of the parsing time has to happen between the previous revision and the current one. It should be part of the performance numbers where you can check historically how this parsing time is behaving. Hot parsing time has to be measured against previous measurements, not against cold parsing times. Same thing for cold parsing times, it has to be measured against previous of-its-kind measurements as well. We basically already do this in oeqa.buildperf.test_basic.Test3. We do "bitbake -p" with cold, "warm" and hot cache. If I'm not mistaken we should close this one as already implemented. marking this as resolved, waiting for QA verification. |