|
Lines 72-77
It is not possible to use all of the suggestions below every single time, but th
Link Here
|
| 72 |
* Remove all non-essential device drivers from the kernel. For instance if USB is not needed for the test, do not put USB in the kernel. Drivers which attach often have timeouts ticking away. |
72 |
* Remove all non-essential device drivers from the kernel. For instance if USB is not needed for the test, do not put USB in the kernel. Drivers which attach often have timeouts ticking away. |
| 73 |
* Unconfigure hardware that are not in use. Detach disks with man:atacontrol[8] and man:camcontrol[8] if the disks are not used for the test. |
73 |
* Unconfigure hardware that are not in use. Detach disks with man:atacontrol[8] and man:camcontrol[8] if the disks are not used for the test. |
| 74 |
* Do not configure the network unless it is being tested, or wait until after the test has been performed to ship the results off to another computer. |
74 |
* Do not configure the network unless it is being tested, or wait until after the test has been performed to ship the results off to another computer. |
|
|
75 |
* Disable "Turbo-modes" because they make the clock frequency explicitly depend on the environment. |
| 75 |
+ |
76 |
+ |
| 76 |
If the system must be connected to a public network, watch out for spikes of broadcast traffic. Even though it is hardly noticeable, it will take up CPU cycles. Multicast has similar caveats. |
77 |
If the system must be connected to a public network, watch out for spikes of broadcast traffic. Even though it is hardly noticeable, it will take up CPU cycles. Multicast has similar caveats. |
| 77 |
* Put each file system on its own disk. This minimizes jitter from head-seek optimizations. |
78 |
* Put each file system on its own disk. This minimizes jitter from head-seek optimizations. |