Matlab r2013a takes long time to respond license#

The first time I opened a file it took 5.6s seconds with most of that time in VideoReader.init. For more information about this process, see the Related Solution 'Why does MATLAB get stuck in the 'Initializing' state or take a long time to start' If there is an LMLICENSEFILE variable set to point to a license server and MATLAB does not use this license server, you can resolve this issue by renaming LMLICENSEFILE to the environment. Browse to the location where you saved the ttings file, select it, and click 'Open'. Double clicking on the file is about 3 times as fast as using the open command, but it uses VideoReader too. In the 'Cluster Profile Manager' window, click the 'Import' button on the toolbar. On my old rig it was about 10 seconds, but my new one takes 1 minute. I have r2013a on a Win7 machine - it has the same problem. Vibrotactile sensory substitution (VSS), which can be used to provide sensory feedback in a non-invasive manner has demonstrated some improvement in myoelectric hand control. When I invoke the matlabpool command it takes an extremely long time to open up each individual worker (the ones you see open in task manager). In this work, we developed and tested two VSS configurations: one with a single burst-rate modulated actuator and another with a spatially distributed array of five coin tactors. We performed a direct comparative assessment of these two VSS configurations with able-bodied subjects to investigate sensory perception, myoelectric control of grasp force and hand aperture with a prosthesis, and the effects of interface compliance. Six subjects completed a sensory perception experiment under a stimulation only paradigm sixteen subjects completed experiments to compare VSS performance on perception and graded myoelectric control during grasp force and hand aperture tasks and ten subjects completed experiments to investigate the effect of mechanical compliance of the myoelectric hand on the ability to control grasp force. This is a known CLR issue and it is unfortunately that it is still not fixed in 4.0.Results indicated that sensory perception of vibrotactile feedback was not different for the two VSS configurations in the absence of active myoelectric control, but it was better with feedback from the coin tactor array than with the single actuator during myoelectric control of grasp force. Setting (can be set through ThreadPool.SetMinThreads). вЂњIf this last I/O thread is used somehow, the ThreadPool would take time to create new threads to handle new WCF requests and also introduced random delays when creating a new thread, even if the number of active threads is smaller than the MinIOthreads It release all of the I/O threads except for one to But this CLR Threadpool has a 15 seconds timeout for idle threads. This spawns worker thread based on the work load. This happens very rarely (about 2-3 times a day).

After checking the logs, I have noticed that the response is sent by the service server in 2 seconds but the client receives it after 1 minute. But sometimes, it takes more than a minute to receive the response on client server. WCF queues up all the calls in a IIS queue which is managed by a CLR IOThreadManager. Generally the response time for the WCF service is less than 2 seconds. There is bug in CLR thus in IIS that restricts WCF to scale up efficiently with bursts of work load.