Thread Subject:

Matlab slow?

Hello - I have a windows 7, Dell precision M6500 with 8 gb of ram and an i7 processor. There are about 5 gb of free space on the c drive.

Even with a new session and no variables allocated (the "whos" command returns nothing), everything takes way too long. A simple "ls" command or even "2+5" can take a few to many seconds.

Any thoughts on why this might be occurring?

Thanks

"John " <matlabuserjq@gmail.com> wrote in message
news:k0m6sl$n4s$1@newscl01ah.mathworks.com...
> Hello - I have a windows 7, Dell precision M6500 with 8 gb of ram and an
> i7 processor. There are about 5 gb of free space on the c drive.
> Even with a new session and no variables allocated (the "whos" command
> returns nothing), everything takes way too long. A simple "ls" command or
> even "2+5" can take a few to many seconds.
> Any thoughts on why this might be occurring?

There are a number of different possibilities that I can think of -- three
are network bottlenecks if MATLAB is not installed locally, slow connections
to the license manager, or an overzealous virus scanner scanning MATLAB
files each time you try to do something.

I'd recommend contacting Technical Support and working with them to
determine the cause of this performance problem.

--
Steve Lord
slord@mathworks.com
To contact Technical Support use the Contact Us link on
http://www.mathworks.com

"John" wrote in message <k0m6sl$n4s$1@newscl01ah.mathworks.com>...
> Hello - I have a windows 7, Dell precision M6500 with 8 gb of ram and an i7 processor. There are about 5 gb of free space on the c drive.
>
> Even with a new session and no variables allocated (the "whos" command returns nothing), everything takes way too long. A simple "ls" command or even "2+5" can take a few to many seconds.
>
> Any thoughts on why this might be occurring?
>
> Thanks


I had the same problem where 1+1 would come back with ans = 2, then the CPU would go to 100% for 10 seconds, delaying any further commands.

As Steven said it could be, it turned out to be something with the network license server.
I switched to a different license server and the problem went away.

Very frustrating for a while there.