The times mentioned here are very rough approximations of what I experience on a pentium M.
-NoDelayComp will load the Media Player, Speech, and Navigation on startup, this will add about 10 seconds to your start time.
-NoDelayLoad will load all the program textures on startup and add about another 10 seconds to your start time.
The default startup loads only the very basic core components needed to run which is basically the layout and a very rough color approximation of all the controls. You might notice texture delay loading in action when you goto a new module you will see just an outline of a control, then half a second later you should notice a full detailed texture that was loaded because it was needed. If you want to see what this looks like, just delete every .PNG file out of skin directory and run StreetDeck. Combinded these optimazation can get you up and running and using StreetDeck in as little as 2 seconds, but you may notice some delays the first time you go to music or navigation as it loads in the components it needs.
If you hibernate or sleep your system, the command line options don't really matter for startup, but it will make a difference if you switch skins or otherwise need to restart StreetDeck.
-NoDelayComp is really a preference of whether you want to wait at startup and get it all out of the way, or if you would rather only load stuff when and if it is needed.
Using -NoDelayLoad generally won't save you any perceivable time or lag while the program is in use as it will only load textures in spare CPU cycles. The only reason you should use it is if you really don't like the artifacts it creates the first time it loads a new module.
^^^yes exactly. so whenever i go into a module its instantly there. I am also running an amd 2ghz processor but i like pusing a button and the command follows quickly. and everytime i get into my car, windows/streetdeck have already loaded since i always remote start my car as im walking to it.