From xemacs-m  Wed Mar 26 13:20:46 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id NAA03269
	for <xemacs-beta@xemacs.org>; Wed, 26 Mar 1997 13:20:44 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcior05319; Wed, 26 Mar 1997 14:20:40 -0500 (EST)
Date: Wed, 26 Mar 1997 14:20:40 -0500 (EST)
Message-Id: <QQcior05319.199703261920@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: 20.1b9 still very slow
In-Reply-To: <199703261901.LAA24907@sandman>
References: <199703261901.LAA24907@sandman>
X-Mailer: VM 6.23 under 19.15 XEmacs Lucid (beta104)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Dan Rich writes:
 > Am I the only one seeing performance problems in the latest 20.1
 > betas?  I timed it yesterday, and on my system it took over 15 seconds 
 > for XEmacs to display a line of text that I typed in an outgoing
 > e-mail buffer (in VM 6.22).  This is built on an UntraSparc 140 with
 > gcc 2.7.2 and X11R6.3.
 > 
 > Running a truss doesn't show anything too interesting, except that it
 > is making hundreds of calls to getcontext().  Is this normal?  Just
 > moving the pointer in and back out of the XEmacs window just caused
 > 417 calls to getcontext in an idle XEmacs process!
 > 
 > Does anyone have any ideas what could be going on?

Didn't we already look at this?  Verdict was "window system
chatter" as I recall.  Presumably your X server is doing soething
the rest of our servers aren't doing.  Check the PROBLEMS file
and look for things Solaris and X related.  I think you're going
to have to debug it, since no one else is complaining.

