Matlab start up very slow

Hi, I am experiencing big issues with Matlab startup. First Matlab(2009b) startup (right after booting) is very slow.

total item gap description

=====================================

 0.00   0.00    0.00   MATLAB script       
 3.64   3.64    0.00   main                
 3.83   0.08    0.12   LM Startup          
 3.85   0.00    0.01   splash              
 4.03   0.00    0.18   mnSigInit           
15.94  405.92    0.00     mljInit           
26.78  10.83    0.00     StartDesktop      
26.78  400.75    0.00   Java initialization 
26.83   0.06    0.00   hgInitialize        
27.88   0.85    0.20   psParser            
28.33   0.24    0.22   cachepath           
30.11   1.13    0.65     matlabpath        
33.71   5.38    0.00   matlabrc            
=====================================
Items shown account for 97.8% of total startup time [TIMER: 3 MHz]

 version -java

ans =

Java 1.6.0_12-b04 with Sun Microsystems Inc. Java HotSpot™ Client VM mixed mode.

If I close and restart Matlab, then startup is much faster (mljInit takes 6.01 seconds)

It seems that there are something wrong with my java. I tried to update java, but nothing works.

I also tried methods on "http://www.mathworks.cn/support/solutions/en/data/1-2Z18MA/index.html" , but nothing works.

any ideas?

[Paulo Silva]

May I ask how did you get those timing values?

[jidg]

run "matlab -timing"

[Paulo Silva]

thanks, here the MATLAB first start takes longer than yours I suspect that the installed toolboxes are the problem

[Fangjun Jiang]

I'm glad to learn this way to measure the MATLAB startup time too. +1

[Matthew M.]

I'm running R2011b (and R2011a) on a Windows 7 32-bit machine. I have exactly the same issue as jidg. When I first start MATLAB after logging on, it takes 3-4 minutes to load, and when I run the timing utility I get the answer that most of the load time results from the Java initialization. If I close and reopen MATLAB it takes only a couple of seconds to load.

[Matthew M.]

FWIW I'm not using any toolboxes at all, so it doesn't seem like toolboxes are the issue.

[Matthew M.]

I deleted my answer because I figured out that the reason my computer was loading MATLAB slowly was that McAfee was running active scans and eating up all the processor time while I was trying to open MATLAB. If I waited until after McAfee was done, MATLAB loaded in a normal time. I tried this in several configurations, with or without the latest Java update installed on my computer, and with or without the MATLAB_JAVA environment variable set to use the updated Java. It doesn't seem to make a difference.

Don't know whether it's just a processor issue for me or if there's some conflict with McAfee. (Stupid administrative software.)

[Darshan Pandit]

I was facing the same problem...tried formatting / reinstalling windows & matlab. No progress...

Then tried adding an exception in antivirus' setting (I've got symmentec) & the trick worked! Thanks for the idea matthew :)

Also, if still someone's facing problems, try visiting following: http://www.mathworks.in/support/solutions/en/data/1-2Z18MA/index.html?solution=1-2Z18MA

Have a good day!

[Kevin]

My experience may help someone.

A year ago I updated from R2010a to R2012a, and my startup time increased from two seconds to ten seconds. Using Wireshark, I noticed that MATLAB was somehow causing NetBIOS WPAD queries (Web Proxy Autodiscovery Protocol) even though web proxy was disabled in MATLAB's Preferences, Web. I don't use a web proxy, so I opened Windows 7's Control Panel, Internet Options, Connections, LAN Settings, and disabled "Automatically detect settings". No more WPAD queries, and MATLAB now starts in two seconds.

[Jan]

Please post this as an answer, Kevin, because saving 8 seconds startup time is a must-have feature.

[legendbb]

Kevin's tip works for my R2013b; I don't know why and how my R2013b booting changed from 2sec to 10sec. I definitely didn't change any system preferences.

But disabling "Automatically detect settings" absolutely helped.

Found a little trace on this issue, it's definitely has something to do with VPN software I have used (CyberGhost).

Thanks for sharing

[Kristjan Jonasson]

I experienced the same. In fact I did some timings (with a watch), with "Automatically detect settings":

         enabled  disabled
  2012a   11 s       4 s
  2012b   10 s       6 s
  2013a    7 s       4 s
  2013b    9 s       5 s

(these are average of 2 or 3 starts, on a new laptop with an SSD drive and I7 processor)