From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Jason Rumney <jasonr@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: Analysis of redisplay performance on Windows
Date: Mon, 28 Jul 2008 13:24:47 +0900 [thread overview]
Message-ID: <wlhcaaab5c.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <488CEE6B.6020600@gnu.org>
>>>>> On Sun, 27 Jul 2008 22:53:47 +0100, Jason Rumney <jasonr@gnu.org> said:
> One difference between Emacs 22 and 23 is that we compute glyph
> indexes properly in Emacs 23, while on 22 we use unicode code
> points. Since we call font->encode_char once per character rather
> than for a whole run, the overhead of selecting fonts into the GC is
> multiplied.
According to the document below, Uniscribe seems to provide some
mechanism to defer heavy operations such as get_frame_dc and
SelectObject.
http://www.microsoft.com/typography/developers/uniscribe/uniscribe.htm#SCRIPT_CACHE
I'm not sure if this retrying with E_PENDING solves the performance
problem on Windows with Uniscribe. But I think it's worth trying
before resorting to platform-independent changes because the
performance problem is not found so far in other platforms including
my local Core Text font-backend driver mentioned in
http://lists.gnu.org/archive/html/emacs-devel/2008-02/msg02186.html.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2008-07-28 4:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 3:07 Analysis of redisplay performance on Windows Chong Yidong
2008-07-27 9:55 ` Jason Rumney
2008-07-27 20:56 ` Chong Yidong
2008-07-27 21:30 ` Jason Rumney
2008-07-27 21:40 ` Chong Yidong
2008-07-27 21:53 ` Jason Rumney
2008-07-28 1:18 ` Chong Yidong
2008-07-28 3:06 ` Adrian Robert
2008-07-28 5:03 ` Chong Yidong
2008-07-28 7:04 ` Jason Rumney
2008-07-28 2:11 ` Kevin Yu
2008-07-28 4:24 ` YAMAMOTO Mitsuharu [this message]
2008-07-28 9:48 ` YAMAMOTO Mitsuharu
2008-07-30 21:51 ` Jason Rumney
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=wlhcaaab5c.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
/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).