From xemacs-m  Mon Dec 16 00:48:12 1996
Received: from mailhost.lanl.gov (mailhost.lanl.gov [128.165.3.12]) by xemacs.cs.uiuc.edu (8.8.3/8.8.3) with ESMTP id AAA21461 for <xemacs-beta@xemacs.org>; Mon, 16 Dec 1996 00:48:11 -0600 (CST)
Received: from xdiv.lanl.gov (xdiv.lanl.gov [128.165.116.106]) by mailhost.lanl.gov (8.8.4/8.8.3) with ESMTP id XAA01066 for <xemacs-beta@xemacs.org>; Sun, 15 Dec 1996 23:48:13 -0700 (MST)
Received: from branagh.lanl.gov (branagh.lanl.gov [128.165.16.72]) by xdiv.lanl.gov (8.6.12/8.6.12) with ESMTP id XAA28284; Sun, 15 Dec 1996 23:48:15 -0700
Received: by branagh.lanl.gov (SMI-8.6/SMI-SVR4)
	id XAA02372; Sun, 15 Dec 1996 23:46:01 -0700
Date: Sun, 15 Dec 1996 23:46:01 -0700
Message-Id: <199612160646.XAA02372@branagh.lanl.gov>
From: John Turner <turner@xdiv.lanl.gov>
To: xemacs-beta@xemacs.org
Subject: Re: 19.15-b4 bench results (get ready...)
In-Reply-To: <199612160501.WAA02208@branagh.lanl.gov>
References: <199612160002.RAA28973@branagh.lanl.gov>
	<m2engrfgsj.fsf@altair.xemacs.org>
	<199612160501.WAA02208@branagh.lanl.gov>
Reply-To: turner@lanl.gov

You're not gonna believe this...

John Turner writes (responding to Steve Bauer):

 >  > Keep turning things off then.  If it isn't lazy-lock, or func-menu it
 >  > must be something else then.  I hope what you meant by `turned off',
 >  > was exiting the program, commenting out the lines in .emacs that turn
 >  > on the specific package and restarting.  All bets are off otherwise.
 > 
 > Definitely.  Everything from clean starts.
 > 
 >  > If you didn't lock up when running in a naked environment, but you did
 >  > when your .emacs is loaded, then you need to isolate which package is
 >  > doing the damage.
 >  > 
 >  > I think if we only get as far as isolating that, it would be an
 >  > enormous improvement.
 > 
 > I know.  I don't look forward to doing this.  If I had finished this
 > msg before my recompile with --debug=no finished I was going to go
 > home.  But the rebuild just finished, so I guess I'll play with it
 > some...

First modified bench.el to just do the 1st 3 tests.

Then I omitted each of the following in turn (independently):

o my .xemacs-options
o scroll-in-place
o all the unbundled stuff I have
o filladapt
o (display-column-mode)

Each time, the display hung during test 3 until C-l.

Then I found it.  Commented out (display-time) -> no hang.

Did (bench 5) just to make sure -> success.

Uncommented it again and watched the time as it executed.  Sure
enough, when the minute changed, it hung.

So is everybody who sees these hangs using (display-time)?  This is
hilarious, because there's really no need for time in the modeline any
more anyway.  This is a relic from my earliest days using Emacs back
in the Emacs 18 days.

Just for clarification, these really aren't hangs per se.  XEmacs just
sits there until it receives some sort of input.  Those of us who see
it have gotten in the habit of just hitting C-l when we think we've
typed something and it isn't showing up.

As for the Hanoi test being 2.5x longer using my .emacs versus -q, I
don't see that any more.  They're slightly slower (15%), but it's not
a big deal, and I don't know what the deal was with those earlier
results.

I'm going to leave a (bench 20) running, and I'll report that
tomorrow...

--
John A. Turner         |"Music is the cup which holds the wine of silence;
Los Alamos Natl. Lab.  |  sound is that cup, but empty;
e-mail: turner@lanl.gov|    noise is that cup, but broken."
                       |                        - Robert Fripp

