Monday, August 07, 2006
Table preview of hotspots (SoC 2006)
Some hotpots combinations were tested. Unexpectedly, the use of several hotspots together didn't cause an arithmetic sum of boot time improvements. For example, let's consider the following hotspots and their corresponding boot times:
On the other side, while trying them together we get:
| hotspot | time |
| DASH AS SH | 4 |
| PRELOADING | 2 |
| NETWORKING | 0 |
| HWCLOCK | 2 |
| REORDERING | 2 |
| PARALLEL | 4 |
On the other side, while trying them together we get:
| hotspot | Test#1 | Test#2 | Test#3 | Test#4 | Test#5 | Test#6 | |
| INSSERV | X | X | X | X | X | ||
| DASH | X | X | X | X | X | X | |
| NETWORKING | X | X | X | ||||
| HWCLOCK | X | X | X | ||||
| PRELOAD | X | X | X | X | X | ||
| PARALLEL | X | X | X | X | |||
| time improve | 4 | 6 | 6 | 6 | 6 | 4 |
# posted by Carlos Villegas @ 4:02 PM 
Comments:
<< Home
Is it all that unexpected?
When you go parallel, networking affects the boot much less since other things get to start in parallel anyway. I guess HWCLOCK is similar.
Post a Comment
When you go parallel, networking affects the boot much less since other things get to start in parallel anyway. I guess HWCLOCK is similar.
# posted by 
: 5:36 PM
: 5:36 PM << Home
