Red Hat Bugzilla – Bug 433263
Slow X11 connections via network
Last modified: 2008-04-17 04:38:53 EDT
Description of problem: When I log-on via a remote X-Server and use graphical applications, some seem to be very slow Steps to Reproduce: 1. Install Fedora-8, accepting all defaults 2. Enable remote XDMCP connections 3. login via an remote X-Server (tried several ones, such as X/Cygwin) 4. Start Eclipse, create project 5. Re-size (maximise ...) are slow, sometimes 5+ seconds. 6. On the console of the server it is running fine and fast 7. Set the variable DISPLAY to localhost:0 and the application becomes much slower. Additional info: During testing we found the 32-bit version of Fedora-8 to work fine. But using an machine with 16GB RAM we need to use the 64-bit version. I tried to update all via yum, but this did not help. And using the alpha-release of Fedora-9 did not help either. I also tried two different machines, but this did not help.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 295273 [details] Xorg config-file
Created attachment 295274 [details] Xorg log for the xorg.conf
Created attachment 295275 [details] Xorg log with no xorg.conf (all probed)
Just to note that there is a large thread on exactly this problem (why is everybody running eclipse over remote X? Did I miss something?) on fedora-devel http://thread.gmane.org/gmane.linux.redhat.fedora.devel/73157 The only (unproven and untested, and without any response in the thread) suggestions were: a) make sure that nothing looking directly or indirectly like 127.0.0.1 is involved b) use freenx (the results on this are rather mixed) However, passing to the developers to see whether they have any idea about this.
I would not say you missed something, but X is a network protocol. You can (and should) use remote X. So we have got our Fedora box on a server-hardware, log-in with some ten users and develop software. Of course using Eclipse as well. Apart from the X problem it is running fine so far and helps to share resources.
X's network layer hasn't changed materially, so I'm inclined to blame network performance problems on the application.
This definitely isn't a CDT issue. I guess one could try an older Eclipse release and see if the problem persists. I don't know what changed with SWT's drawing or whatever so that'll require some investigation, I guess. Torsten: does this happen with upstream downloads of eclipse as well? If so, we should really file this there.
Well to be honest using Eclipse 3.2 it works fine, but 3.3 is slow. Nevertheless we have to some other home-made java apps (sing) that are *very* slow, too. And the overall impression is: The 64-bit system displays graphics noticably slower than the 32-bit. So I am a bit stuck to say who is guilty. Maybe X, gtk, java or whatever.
Okay, let's try to isolate some variables. Try the following: upstream eclipse 3.2 on F8 with IcedTea upstream eclipse 3.3 on F8 with IcedTea Is 3.3 slower than 3.2? If so, it looks like an upstream issue. upstream eclipse 3.2 on F8 with IcedTea upstream eclipse 3.2 on F8 with the Sun JVM Is it slower with IcedTea? upstream eclipse 3.2 on F7 with the Sun JVM upstream eclipse 3.2 on F8 with the Sun JVM Is it slower on F8? upstream eclipse 3.3 on F8 with IcedTea Fedora eclipse on F8 with IcedTea Is Fedora Eclipse slower? If so, it looks like some (I don't know how) issue in Fedora Eclipse.
Hello again ... sorry for the delay, but I needed to do some other work first. The simple answer to all your questions is: * Eclipse 3.2 is much faster than 3.3 * I cannot see a difference between Eclipse (from Eclipse.org) and Fedora-Eclipse * I cannot see a difference with different VMs (IcedTea, Sun, 32-bit, 64-bit) * Eclipse on F7 seems faster than on F8 * Eclipse on F8-32bit seems faster than on F8-64bit.
(In reply to comment #11) > Hello again ... sorry for the delay, but I needed to do some other work first. No problem. Thanks for testing! > * Eclipse 3.2 is much faster than 3.3 Okay. > * I cannot see a difference between Eclipse (from Eclipse.org) and Fedora-Eclipse Good. > * I cannot see a difference with different VMs (IcedTea, Sun, 32-bit, 64-bit) Good. > * Eclipse on F7 seems faster than on F8 F7 had 3.2.x and F8 has 3.3.x. > * Eclipse on F8-32bit seems faster than on F8-64bit. Odd. I think at this point we need to move this upstream, since it looks like something changed in SWT (Eclipse's widget toolkit) or SWT's gtk interaction. If you're sure that 3.2.x is noticeably faster on F8 than 3.3.x is (upstream downloads in all cases), file a bug at bugs.eclipse.org against Platform->SWT and CC me, please. When you've filed it, mark this as upstream and put a reference to the bug here. Thanks, Torsten!
There are several bug-entries @eclipse, so one is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=104271
Ah, after some more debugging I found the real problem. This is already described in: https://bugzilla.redhat.com/show_bug.cgi?id=442158 So I am closing this as a dublicated of the bug above, *** This bug has been marked as a duplicate of 442158 ***