Very Computer

Hello,

I have a suite of Motif applications that perform well under the following operating
systems / X-Servers:

     SunOS OpenWindows and MIT X11R4 and X11R5
     UnixWare 2.0
     Linux
     HPUX 9.03 +
     AIX 3.2 +

I recently ported it to Solaris 2.4.  It was compiled using gcc 2.6.3 .  The
Motif libraries are Version 1.2 from Sun (through IXI).  Version 1.2.2 is on order.

Some screens are running *way* too slow.  Using the Solaris 2.4 compilation, there
are a couple of screens that take about 60 seconds to repaint after they have been
resized. On all the other platforms, these same screens take 2 or 3 seconds to
repaint. The only thing I see as different about the real slow screens from all the
other screens that repaint at a reasonable rate is that they have a lot of XmText
widgets.  The hardware platforms are identically configured in both cases: Sun Sparc
1+ systems with 32MB memory and plenty of disk and swap space.

Has anyone else experienced this?  Any ideas why the screens with a lot of XmText
widgets repaint so slow?

Any suggestions would be appreciated.

-Steve Mansour

Have you tried using the Motif 1.2.3 that comes with Solaris 2.4?

Another thing I've seen happen in Solaris 2.4 is slow repaints on
remote displays (i.e., when you use TCP for the connection).
We determined that that was caused by patch 101969-05.
(Which is superceded by kernel patch 101945-27 which fixes this problem)

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.

Quote:>Has anyone else experienced this?  Any ideas why the screens with a lot
of XmText
>widgets repaint so slow?

How many is "a lot".  Early releases of Motif 1.2.X had a problem with
drag-and-drop initilization for text widgets.  You could try disabling
drag-and-drop for these widgets.  Or, upgrade to a more recent release.

Ken

_______

: Bingo.  If you're concerned about speed, don't use gcc to compile.  As far
: as solaris goes, gcc is better for debugging purposes, but cc creates faster
: executables because it does a better job at optimization.

I'm afraid my experience is exactly opposite. I generally find Sun's cc to
produce slower code than gcc, assuming both are given the appropriate
optimization flags. However, most of my stress tests have been highly
numerical, so that may skew things. YMMV.

Of course, if you really want fast code, from what I've seen the Artecon
compiler is the one you want.

: >I recently ported it to Solaris 2.4.  It was compiled using gcc 2.6.3 .  The
: >Motif libraries are Version 1.2 from Sun (through IXI).  Version 1.2.2 is on order.

Bingo.  If you're concerned about speed, don't use gcc to compile.  As far
as solaris goes, gcc is better for debugging purposes, but cc creates faster
executables because it does a better job at optimization.

--
Matt Inger

http://mcs.drexel.edu/~uminger/
"Remember when you were young?  You shone like the sun."