Xmanager 1.3.9 slower in RedHat 7.3 [3]

Hi, I switched from RedHat 7.1 to 7.3 and found that
Xmanager sessions are a little slower on their repaint/scren refresh
side.
I can notice it when dragging or resizing windows or when scrolling.

Another experiment:
When running the JBuilder 7 IDE under jdk1.4 (I know it's
supported only up to 1.3.. but still :-) directly from the linux
machine, it works much slower, but when running it thourgh
Xmanager it becomes unusable.. in fact, the whole Xmanager
session becomes slooooooooowwwwwwwwwww, having to wait for at least
half a minute just to switch to another window or to kill J Builder or any other kind of mouse events. Also there are lots of window
repaint problems.

Interestingly, while using VNC JBuilder7 + jdk 1.4 runs OK.
A little slower, yes, because of VNC's inefficiency, but no repaint
problems at all... That¿ even better than I get directly frorm the linunx console!!
Incredible, eh?

Anyway, I dont like Xmanager having repaint problems or freezing up my screen because one application (JBuilder) may be doing something strange. Also I dont know where the general slowness came from when switching from RH 7.1 to RH 7.3

I'd like some comments about this phenomena.

Barcho

JBuilder 7 IDE under jdk1.4 might consume lots of system resources so that Xmanager is slowed down with endless disk swapping.

We are working on this matter and will post the result in a couple of days.

----
Technical Support

>JBuilder 7 IDE under jdk1.4 might consume lots of system resources >so that Xmanager is slowed down with endless disk swapping.
>
>We are working on this matter and will post the result in a couple >of days.


I'll try to explain a little better.

1) I don't think it's a question of JBuilder consuming resources
because if I sit directly at the linux terminal everything is working normally at the same time that Xmanager on the PC is crawling painfully. Consider also the fact that viewing the same combination of JBuilder plus jdk1.4 works much better though VNC which is inherently less efficient but at least it doesn't freeze.
I think (knowing nothing about the X protocol :-) it's more a matter of something the application is sending to the X server that confuses Xmanager.
Incidentally, I just tested the SwingSet2 demo that comes with JDK1.4
to see if it was something related to the inefficency of Swing in
general, but it works fine.

2) Xmanager is a little slower (window resizing, dragging, for instance) for RedHat 7.3 than what it was for RedHat 7.1.
It may be a matter of a new version of XFree86.... (There's also a
new version of KDE in RH 7.3 but I think the same problem occurs
while using Gnome).
This second issue is for the *whole* Xmanager, doesnt matter whether
you're running JBuilder.

Try this: in file JBuilder7/bin/jdk.config comment out the line
that says:
addbootpath ../lib/TabbedPaneFix.jar

This should improve things a tiny bit, at least from the console and from VNC it becomes *almost* usable. From Xmanager it's still a pain.
But maybe this tip will guide you to the problem??

3) I think issues (1) and (2) are completely unrelated because
the problem with JBuilder and jdk1.4 existed back in RH7.1
but the general slowness didn't


Thanks a lot for the opportunity to improve Xmanager

Thanks for your time and effort.

We've tested Jbuilder with a jdk1.4 installed.

The slow response is due to a complex region operation in jdk1.4 and it can be fixed in future Xmanager. In the mean time, you can fix it by configuring Backing Store option in Xconfig. By configure Backing Store to "When Mapped" and the response time will be improved.

We also ran Jbuilder on the console. Jbuilder via jdk1.4 showed a screen refresh problem and overally, we could't use Jbuilder normally.

And overall slowness in RedHat 7.3 was not significant in our environment. A little bit slow, but it worked well for normal operations. We need more tests for this problem.

In summary, Jbuilder 7 via jdk1.4 doesn't match well with Xmanager currently. We will try to fix the problem but in part Jbuilder 7 should also be upgraded for jdk1.4.

We hope this can help you.

----
Technical Support