- Timestamp:
- 08/30/2024 04:01:29 AM (3 weeks ago)
- Branches:
- xry111/clfs-ng
- Children:
- 82220a5
- Parents:
- 2b63974 (diff), 73f24ad (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/aboutsbus.xml
r2b63974 r134440b 27 27 28 28 <para>For example, consider a package whose compilation time is 4.5 29 SBUs. This means that if your system took 10minutes to compile and29 SBUs. This means that if your system took 4 minutes to compile and 30 30 install the first pass of binutils, it will take 31 <emphasis>approximately</emphasis> 45minutes to build the example package.31 <emphasis>approximately</emphasis> 18 minutes to build the example package. 32 32 Fortunately, most build times are shorter than one SBU.</para> 33 33 … … 36 36 to give an estimate of how long it might take to install a package, but the 37 37 numbers can vary by as much as dozens of minutes in some cases.</para> 38 39 <para>On some newer systems, the motherboard is capable of contolling 40 the system clock speed. This can be controlled with a command such as 41 <command>powerprofilesctl</command>. This is not available in LFS, but 42 may be available on the host distro. After LFS is complete, it can be 43 added to a system with the procedures at the 44 <ulink url='&blfs-book;sysutils/power-profiles-daemon.html'> 45 BLFS power-profiles-daemon</ulink> page. 46 47 Before measuring the build time of any package it is advisable to use a 48 system power profile set for maximum performance (and maximum power 49 consumption). 50 51 Otherwise the measured SBU value may be inaccurate because the 52 system may react differently when building <xref linkend='ch-tools-binutils-pass1'/> 53 or other packages. 54 55 Be aware that a significant inaccuracy can still show up even if the same 56 profile is used for both packages because the system may respond slower if 57 the system is idle when starting the build procedure. Setting the power 58 profile to <quote>performance</quote> will minimize this problem. And 59 obviously doing so will also make the system build LFS faster.</para> 60 61 <para>If <command>powerprofilesctl</command> is available, issue the 62 <command>powerprofilesctl set performance</command> command to select 63 the <literal>performance</literal> profile. Some distros provides the 64 <command>tuned-adm</command> command for managing the profiles instead of 65 <command>powerprofilesctl</command>, on these distros issue the 66 <command>tuned-adm profile throughput-performance</command> command to 67 select the <literal>throughput-performance</literal> profile.</para> 38 68 39 69 <note> … … 53 83 single processor build to properly analyze the error messages.</para> 54 84 55 <para>The times presented here are based upon using four cores (-j4). The 85 <para>The times presented here for all packages 86 (except <xref linkend='ch-tools-binutils-pass1'/> which is based on one core) 87 are based upon using four cores (-j4). The 56 88 times in Chapter 8 also include the time to run the regression tests for 57 89 the package unless specified otherwise.</para> 58 59 90 </note> 60 91
Note:
See TracChangeset
for help on using the changeset viewer.