From: Chong Yidong <cyd@stupidchicken.com>
To: Kenichi Handa <handa@m17n.org>
Cc: Adrian Robert <Adrian.B.Robert@gmail.com>, emacs-devel@gnu.org
Subject: Re: Analysis of redisplay performance on Windows
Date: Mon, 28 Jul 2008 01:03:50 -0400 [thread overview]
Message-ID: <87fxpueh1l.fsf@stupidchicken.com> (raw)
In-Reply-To: <loom.20080728T030223-98@post.gmane.org> (Adrian Robert's message of "Mon, 28 Jul 2008 03:06:16 +0000 (UTC)")
Adrian Robert <Adrian.B.Robert@gmail.com> writes:
> In the NS font driver (nsfont.m) these two functions cache info for
> each font by block of 256 (stored in nsfont_info -- nsterm.h). This
> made a significant different in rendering speed when I implemented it,
> and the memory cost is not high unless lots of different char ranges
> are being rendered in lots of different fonts. Moving this code up to
> font.c would be another option to consider.
If we go this route, it's probably faster to reimplement this cache
separately for w32, using the NS code as a guide and keeping it as close
as possible. Working with the platform-independent code, you'd have to
worry about screwing things up on other platforms. We can always
consolidate/refactor the code in the next development cycle.
Handa, do you have any comments about the nsfont_info mechanism that
Adrian pointed to?
next prev parent reply other threads:[~2008-07-28 5:03 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 [this message]
2008-07-28 7:04 ` Jason Rumney
2008-07-28 2:11 ` Kevin Yu
2008-07-28 4:24 ` YAMAMOTO Mitsuharu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fxpueh1l.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=Adrian.B.Robert@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.