From xemacs-m  Mon Feb 24 16:43:28 1997
Received: from pat.idt.unit.no (0@pat.idt.unit.no [129.241.103.5])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id QAA19490
	for <xemacs-beta@xemacs.org>; Mon, 24 Feb 1997 16:43:26 -0600 (CST)
Received: from ynde.idt.unit.no (1466@ynde.idt.unit.no [129.241.200.28])
	by pat.idt.unit.no (8.8.5/8.8.5) with ESMTP id XAA11432
	for <xemacs-beta@xemacs.org>; Mon, 24 Feb 1997 23:43:21 +0100 (MET)
Received: (from palat@localhost)
	by ynde.idt.unit.no (8.8.5/8.8.5) id XAA04792;
	Mon, 24 Feb 1997 23:43:18 +0100 (MET)
Sender: Sudeep.Palat@item.ntnu.no
To: xemacs-beta@xemacs.org
Subject: lazy lock cpu usage
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
From: Sudeep Kumar Palat <Sudeep.Palat@item.ntnu.no>
Date: 24 Feb 1997 23:43:17 +0100
Message-ID: <yv9bu99hlkq.fsf@ynde.idt.unit.no>
Lines: 22
X-Mailer: Gnus v5.4.15/XEmacs 20.1

I do not know if this is the expected behaviour, but thought it might
be worth reporting.

Start xemacs -q and load a large file, for e.g., gnus.el.  Turn on
font lock.  Hold down the cursor key and look at cpu usage (I used
top).  When the buffer has scrolled down 20%, the cpu usage by XEmacs
is about 14% (it keeps increasing, presumably because, XEmacs is
unable to process the key input at the keyboard repeat rate).

Turn on lazy lock, and repeat.  Scrolling 20% down, the cpu usage has
shot up to about 50%.

XEmacs 20.1b2, no mule, on sun-sparc 5, solaris 2.5.

Changing over to fast lock from lazy lock for my rather large latex
file was the best thing I did since I moved over to XEmacs :-)

sudeep




