For instance, here's a boot scenario that uses the default waitfor order. As you can see, there are a couple of gaps (at about 130 ms and 400 ms) where nothing executes while a waitfor waits for a resource to become available:

Now here's the same system, but with optimized waitfor placement. As you can see, changing the order of waitfor statements has largely eliminated the idle gaps, shaving over 100 milliseconds off the boot time:

No comments:
Post a Comment