| Summary: | gettext:do_configure takes longer than expected | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | core | Assignee: | Ross Burton <ross.burton> |
| Status: | VERIFIED NOTABUG | QA Contact: | Valentin Hangan <valentinx.hangan> |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher, valentinx.hangan |
| Version: | 2.0 | ||
| Target Milestone: | 2.1 M3 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2015-11-18 16:15:46 UTC
gettext is a pathological case (something like five nested configures). 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. Proposing to close this: gettext takes a long time as it runs configure five or so times. Stupid, but true. Close as NOTABUG Verified as NOTABUG |