Wifi needs up to 30 sec. to connect after sleep

Question

The title exactly describes the problem. The wifi  connection of my  MAC book pro (late 2013)  will take up to 30 seconds to  connect to my WLAN after sleep. Maybe it is a problem since Yosemite but I don´t know exactly. Does anybody has the same problem or maybe a solution?
Regards, Lidira

Answer 1

There are many factors in startup time. The first time you create the engine there should be a short delay as lots of things are going on, dlls are loaded, global variables and configuration files are loaded and internal data structures are created. When Start() is called, additionally the loginlogout callback might be launched. 20-30 seconds does seem a bit long though for any modern machine (I'd expect more on the order of 2-5 seconds on a reasonably fast computer for creating the engine) so something else might be going on in your system. Do you perhaps have a lot of global variables, are a lot of VIs being loaded by the loginlogout callback perhaps and perhaps being mass compiled by labview? Is your login callback perhaps hanging on an instrument driver call until a timeout occurs? There are many many possibilities. Have you tried launching a UI or seqedit.exe on a clean install of teststand on that machine? If so how long does that take? If it's much faster than 20 - 30s, then the extra time must be due to customizations you have made. If so, try systematically removing or commenting out customizations to narrow down where the problem is. If on a clean install of teststand it still always takes 20-30seconds to create the engine, then there might be something unusual about your machine that will need to be narrowed down (assuming it isn't just an usually old or slow computer). Have you seen this significant a slowdown on all of your machines or only on certain ones?
Also keep in mind that the OS does lots of caching of things, so the first time dlls are loaded is often much slower that subsequent times.
Also keep in mind that .NET applications startup slower than non-.NET application (especially the first time one is launched after rebooting) as there is a significant amount of overhead involved. This is something Microsoft has been working on improving for future versions of the .NET framework.
Hope this helps,
-Doug