--=-=-=
Content-Transfer-Encoding: quoted-printable


Christian Biere <christianbiere@gmx.de> writes:

> Hauke Fath wrote:
>> The machines offer KDE, Gnome, XFCE4 and your favourite window=20
>> manager as environment via gdm, but the problem seems to concern all=20
>> of them. As an example, when I log in to XFCE4, first opening of a=20
>> popup menu from xfce4-panel takes 15 sec on an AMD 700 MHz / 384 MB=20
>> RAM. During that time, system load is around 2, there are still > 100=20
>> MB RAM unused, there is disk activity, and xfce4-panel is busy=20
>> consuming cpu time. The next menu then appears instantaneously.=20
>> Similar under Gnome: A Gnome terminal takes around 15 sec to appear,=20
>> a KDE konsole 20 sec, and even an xterm needs 10 sec.
>
> Have you traced them? Font loading time is very likely the issue. My
> apps seemingly spent most and too much time at that step as well. Albeit
> it's not as horrible as in your examples.

I had trouble with gqview taking a long time to start up.  Rebuilding
fontconfig caches with fc-cache (as root) turned out to be the
required step to fix it.

But, xterm taking a long time doesn't fit this theory - it doesn't
AFAIK use fontconig.

Another thing to check is DNS, but that doesn't fully fit either.

=2D-=20
    Greg Troxel <gdt@ir.bbn.com>

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)

iD8DBQFFdbpl+vesoDJhHiURAnW1AKCTK8Kv7sQZEjnlGVKvLQTW8ll6TQCgkTqp
KeOmZ4g7Fz1TyD5fAaSDVS8=
=FtpJ
-----END PGP SIGNATURE-----
--=-=-=--