Changeset bfa21f3 for introduction/welcome/conventions.xml
- Timestamp:
- 10/17/2014 02:17:11 AM (10 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 6000a3e
- Parents:
- 16890f2
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/welcome/conventions.xml
r16890f2 rbfa21f3 124 124 </sect2> 125 125 126 <sect2> 127 <title>SBU values in BLFS</title> 128 129 <para>As in LFS, each package in BLFS has a build time listed in Standard 130 Build Units (SBUs). These times are relative to the time it took to build 131 binutils in LFS and are intended to provide some insight into how long it 132 will take to build a package. Most times listed are for a single processor 133 or core to build the package. In some cases, large, long running builds 134 tested on multi-core systems have SBU times listed with comments such 135 as '(parallelism=4)'. These values indicate testing was done using 136 multiple cores. Note that while this speeds up the build on systems with 137 the appropriate hardware, the speedup is not linear and to some extent 138 depends on the individual package and specific hardware used. </para> 139 140 </sect2> 141 126 142 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.