Bug 10743 - build-perf-test: Add test to verify if parsing time is improved with a hot codeparser cache
Summary: build-perf-test: Add test to verify if parsing time is improved with a hot co...
Status: RESOLVED FIXED
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.3
Assignee: Markus Lehtonen
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-11-30 14:01 UTC by Jose Perez C
Modified: 2017-12-06 17:18 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jose Perez C 2016-11-30 14:01:09 UTC 
A proposal to implement this is to take measurements of `bitbake -e` first time and then run again `bitbake -e` and check the improvement on the parsing time.
Comment 1 Benjamin Esquivel 2016-11-30 16:30:14 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.
Comment 2 Markus Lehtonen 2016-12-01 09:02:47 UTC 
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.
Comment 3 Benjamin Esquivel 2016-12-01 15:51:25 UTC 
marking this as resolved, waiting for QA verification.