From: Kenichi Handa <handa@ni.aist.go.jp>
To: Martin Pohlack <mp26@os.inf.tu-dresden.de>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: extremely slow font-lock-mode
Date: Wed, 12 Dec 2007 13:25:58 +0900 [thread overview]
Message-ID: <E1J2JAU-00047f-Dp@etlken.m17n.org> (raw)
In-Reply-To: <475F2981.6030108@os.inf.tu-dresden.de> (message from Martin Pohlack on Wed, 12 Dec 2007 01:21:21 +0100)
In article <475F2981.6030108@os.inf.tu-dresden.de>, Martin Pohlack <mp26@os.inf.tu-dresden.de> writes:
> [1 <text/plain; ISO-8859-15 (7bit)>]
> martin rudalics wrote:
>>> I'm experiencing very slow syntax highlighting with emacs-23.0.60
>>> (GTK+ Version 2.12.1)a.
>>>
>>> Simply scrolling in source files takes incredibly long (~ 1 second for
>>> scolling one line backwards). This is an a dual-core 2 GHZ machine
I recentry modified handle_auto_composed_prop in
emacs-unicode-2. There's a possibility that it is the
culprit. Please try to turn off auto-composition-mode.
> Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit \
> mask of 0x00 (Unhalted core cycles) count 240000
> samples % symbol name
> 48798 32.2244 lookup_char_property
> 37434 24.7200 next_interval
> 24605 16.2482 get_property_and_range
Hmmm, in handle_auto_composed_prop, get_property_and_range
is called twice, and such a file as entry-ia32-ux.S causes
freguent face change which leads to lots of calling
handle_auto_composed_prop.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2007-12-12 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 10:25 extremely slow font-lock-mode Martin Pohlack
2007-12-11 22:32 ` martin rudalics
2007-12-12 0:21 ` Martin Pohlack
2007-12-12 4:25 ` Kenichi Handa [this message]
2007-12-12 8:22 ` Martin Pohlack
2007-12-12 11:06 ` Kenichi Handa
2007-12-12 8:37 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1J2JAU-00047f-Dp@etlken.m17n.org \
--to=handa@ni.aist.go.jp \
--cc=emacs-devel@gnu.org \
--cc=mp26@os.inf.tu-dresden.de \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).