Changeset 406e5ffe for introduction/welcome/conventions.xml
- Timestamp:
- 04/05/2018 10:31:16 PM (6 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, 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:
- 20a27fc
- Parents:
- b81acc38
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/welcome/conventions.xml
rb81acc38 r406e5ffe 235 235 depends on the individual package and specific hardware used. </para> 236 236 237 <para>For packages which use ninja (e.g. anything using meson) or rust, by 238 default all cores are used so similar comments will be seen on such packages 239 even when the build time is minimal.</para> 240 237 241 <para>Where even a parallel build takes more than 15 SBU, on certain 238 242 machines the time may be considerably greater even when the build does not 239 use swap.</para> 243 use swap. In particular, different micro-architectures will build some 244 files at different relative speeds and this can introduce delays when 245 certain make targets wait for another file to be created. Where a large 246 build uses a lot of C++ files, processors with Simultaneous Multi Threading 247 will share the Floating Point Unit and can take 45% longer than when using 248 four 'prime' cores (measured on an intel i7 using taskset and keeping the 249 other cores idle).</para> 240 250 241 251 <para>Some packages do not support parallel builds and using -j1 for the
Note:
See TracChangeset
for help on using the changeset viewer.