Bug 8702 - gettext:do_configure takes longer than expected
Summary: gettext:do_configure takes longer than expected
Status: VERIFIED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.0
Hardware: All Multiple
: Medium+ normal
Target Milestone: 2.1 M3
Assignee: Ross Burton
QA Contact: Valentin Hangan
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-11-18 16:15 UTC by Ross Burton
Modified: 2016-05-04 10:47 UTC (History)
3 users (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 Ross Burton 2015-11-18 16:15:46 UTC 
For some reason gettext:do_configure takes a very long time to run.  We should investigate this.
Comment 1 Ross Burton 2015-12-21 21:33:10 UTC 
gettext is a pathological case (something like five nested configures).
Comment 2 Ross Burton 2016-01-26 17:28:21 UTC 
Interim conclusion:

* gettext configure is pathological with five nested configure scripts

* configure on contemporary x86 hardware is pathological as the scheduler puts each new process (thousands involved) on a fresh core, for me resulting in 20 cores running at 5% usage at the lowest frequency, taking 90 seconds.  Using taskset -c0 (outside of bitbake) results in a single CPU running at turbo'd 100% CPU, taking 40 seconds.
Comment 3 Ross Burton 2016-03-21 22:58:00 UTC 
Proposing to close this: gettext takes a long time as it runs configure five or so times. Stupid, but true.
Comment 4 Valentin Hangan 2016-05-04 10:44:19 UTC 
Close as NOTABUG
Comment 5 Valentin Hangan 2016-05-04 10:47:43 UTC 
Verified as NOTABUG