From: Madhu Shurpali on 24 Dec 2009 00:52 Hello, I have installed MATLAB on WindowsXP with a 64 bit platform. The problem is MATLAB takes a lot for time to boot up. As much as 10 mins sometimes. Can somebody suggest as what can be done to improve the startup time. (I know that this is a Tech support issue, but since my organisation not under maintainence I had to post on this forum). Thanks Madhu
From: Jan Simon on 24 Dec 2009 04:45 Dear Madhu! > I have installed MATLAB on WindowsXP with a 64 bit platform. > > The problem is MATLAB takes a lot for time to boot up. As much as 10 mins sometimes. Can somebody suggest as what can be done to improve the startup time. Are there any time-consuming tasks in STARTUP.M? You can insert some "disp(clock)" command in MATLABRC.M to find out, where the unexpected processing appears. I think, PROFILE is not available at this stage. If the source files of your toolboxes are located on a slow network drive and toolbox caching is disabled, such effect can be possible. Enable toolbox caching then... Good luck, Jan
From: Madhu Shurpali on 28 Dec 2009 05:29 > Are there any time-consuming tasks in STARTUP.M? > You can insert some "disp(clock)" command in MATLABRC.M to find out, where the unexpected processing appears. I think, PROFILE is not available at this stage. > > If the source files of your toolboxes are located on a slow network drive and toolbox caching is disabled, such effect can be possible. Enable toolbox caching then... > > Good luck, Jan The Startup.m had the following lines. I couldnt make much out of it. %%%%%%%%%%%%%%%%%% close all force; try bdclose('all'); end clear all; %%%%%%%%%%%%%%%%%%% I Enabled Toolbox caching by doing File->Preferences->Enable Toolbox .. The following lines were displayed while the MATLAB was starting: Toolbox Path Cache read in 0.00 seconds. MATLAB Path initialized in 0.22 seconds. After the display of these two messages, it took a lot of time for the MATLAB Command prompt to appear. Is there anything else that I need to do to expediate the booting of MATLAB. FYI.. I have MATLAB 2007 and 2008 installed. All the above steps were done on both the versions. Thanks
From: Jan Simon on 28 Dec 2009 20:15 Dear Madhu! > The Startup.m had the following lines. I couldnt make much out of it. > close all force; > try > bdclose('all'); > end > clear all; It is really unlikely, that CLOSE and CLEAR is needed at startup. I do not know BDCLOSE. But please try to disable all these lines by commenting them out. Good luck, Jan
From: nanren888 on 28 Dec 2009 21:28
Jan Unless you're in some environment that installs stuff for you, eg matlabrc.m &c.; There doesn't seem to be anything much in your startup.m that you need. Maybe you could just temporarily rename startup.m to startupOld.m & see if Matlab still takes an age to start. If so, then at least you've learned that it's not startup.m. Using clock, tic or toc &c. you could maybe see where the time goes, eg in startup, in matlabrc, somewhere before that, somewhere after that? In my setup at work, our IT guys, in their infinite wisdom make me start on some home drive in some server, way the heck somewhere else. Matlab starts there & takes time to start as it does whatever it does when it starts, involving (my suspicion) using directories, that are at the end of a slow-to-establish network connection. Any help? |