GUI Extremely Slow on Remote Machines (Linux)
Ephraim
When running the GUI locally, response time is fine.
When running remotely without the GUI (-nojvm), response
time is fine.
When running remotely with the GUI, response time is
atrocious (almost a minute just to move between subwindows)
even though the remote Linux machine is much stronger than
than the local host.
Other GUI applications other than Matlab give good response
time when run remotely so the network is not the problem.
The problem persists over a variety of Window managers (e.g.
fvwm, ctwm, icewm, xfce).
Any ideas/pointers would be appreciated.
Ephraim
Walter Roberson
Ephraim <ephraim...@cs.huji.ac.il> wrote:
>We run Matlab 2007a on Linux Debian Lenny 32 bit machines.
>When running the GUI locally, response time is fine.
>When running remotely without the GUI (-nojvm), response
>time is fine.
>When running remotely with the GUI, response time is
>atrocious (almost a minute just to move between subwindows)
>even though the remote Linux machine is much stronger than
>than the local host.
>Other GUI applications other than Matlab give good response
>time when run remotely so the network is not the problem.
It -is- a network issue: you are seeing *very* bad latencies
as Matlab communicates with your local X server.
I have seen the same effect when I run Matlab at work, displaying
at home over an ssh tunnel. I have timed a few times: over 70
seconds just to minimize the command window and have the editor
underneath repaint and come to attention. Trying to do real work
through that delay is very trying on one's patience.
The workaround we have found is to use vnc: we have a vnc server
on the remote machine providing a window manager that is local
to that server, and our vnc client (could be remote) talks to the
vnc server. Response time is really very reasonable, even over
a residential cable connection.
--
"Any sufficiently advanced bug is indistinguishable from a feature."
-- Rich Kulawiec
Holger Friedrich
did you get this issue resolved?
We have exactly the same problem after upgrading to new
server hardware (gigabit ethernet network, a64 xeon
machine).
Local access works just fine, as vnc does also.
SSH access (linux client, x86) is very slow; updating menu
dropdown takes about 1 second. Can't work....
Holger
Ephraim
> did you get this issue resolved?
Not exactly -- the official response was:
"Mathworks do not officially support launching MATLAB from a
remote machine."
> Local access works just fine, as vnc does also.
> SSH access (linux client, x86) is very slow; updating menu
> dropdown takes about 1 second. Can't work....
Beyond the official response above, they suggested using
VNC or SSH with the DISPLAY set to IPaddressHere:0.0 of
the local workstation. The SSH suggestion did not result in
any significant improvement.
Ephraim
i-me Budumlu
Hello,
maybe I found a resolution for this problem! Just put a file called "java.opts" containing the Java option "-Dsun.java2d.pmoffscreen=false" into the directory *matlabroot*/bin/*system*/
On our system (opensuse 10.3) this solves the problem!
i-me
Holger Friedrich
> Hello,
>
> maybe I found a resolution for this problem! Just put a file called "java.opts" containing the Java option "-Dsun.java2d.pmoffscreen=false" into the directory *matlabroot*/bin/*system*/
>
> On our system (opensuse 10.3) this solves the problem!
>
> i-me
>
I confirm. This works fine!
Thanks
Holger
James
My GUI was also very slow (running locally), and would cause XOrg use to spike.
Just a note: there was no "system" directory in my installation, so I created it.
Thanks for figuring this out!
James
"Holger Friedrich" <holger.frie...@vsi.cs.uni-frankfurt.de> wrote in message <go6s4h$hmc$1...@fred.mathworks.com>...
James
"James " <james....@colorado.edu.REMOVETHIS> wrote in message <gpeigd$gd4$1...@fred.mathworks.com>...
Benjamin
> Just one more note: I had to run MATLAB from the system directory I just created for this to work. Just calling the matlab executable normally didn't do it. I made a shell script to change the directory, then call MATLAB.
May be you misunderstood the directory name "system". It has to be replaced by the short description of the architecture. On a Linux 64-bit system it is "glnxa64". The full directory name is for instance "/opt/Matlab/R2008b/bin/glnxa64". With this configuration, regardless where I start Matlab from, the java.opts file is always considered.
Peter Cendula
I put java.opts exactly where you said, "matlab71/bin/glnxa64". I have R14SP3 release on Ubuntu 8.04
If I start matlab from "bin" system directory or by link to it from any other directory,
it's still the same slow (1-2s delay) over ssh. If I start other java application (Comsol), the delay is not noticable over SSH (<few ms).
Does anybody have a clue?
Thanks
Peter
Thomas
I only know how to fix this in Ubuntu:
1. download old versions of the libx11-6 and libx11-dev packages.
Go to these two pages, click on version 1.0.3-4ubuntu1, and download the .deb from the next page
https://launchpad.net/ubuntu/feisty/amd64/libx11-6
https://launchpad.net/ubuntu/feisty/amd64/libx11-dev
(those are the amd64 packages, for other architectures substitute "amd64" with "i386" or "ia64" or whatever)
2. Install those packages.
Go to the directory where you downloaded them, and run
sudo dpkg -i libx11*.deb
3. Put something in your /etc/apt/preferences, so that the packages aren't upgraded again, next time you install something.
My /etc/apt/preferences has the following contents:
# Newer versions (1.1.*) of libx11 make MATLAB super slow, so we use
# a version from Feisty.
Package: libx11-6
Pin: version 1.0.3*
Pin-Priority: 1001
Package: libx11-data
Pin: version 1.0.3*
Pin-Priority: 1001
The Pin-Priority has to be 1000 or higher for apt to decide to leave something downgraded.
Hope this helps.