From: Jan Simon on
Dear nanren888!

> 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.

I cannot follow you.
Do I understand correctly: Your IT guys let you work over a slow network?
Then the help is trivial: Tell the IT guys, that the current setup is too slow for efficient working. Then it's their job to install an environment, which let you do your job.

Kind regards, Jan
From: Madhu Shurpali on
Well I feel IT guys are the equivalent of Lawyers at our work environement.

I could improve the speed of the MATLAB boot, by implementing the suggestions above. In addition to that I saved only the last 5 working directories - default is 20.