From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: emacs-devel@gnu.org
Subject: Display performance degradation
Date: Thu, 17 Dec 2009 11:49:01 +0900 [thread overview]
Message-ID: <wlmy1iuxgi.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
I can observe significant display performance degradation on Emacs
23.1.90 compared with 23.1, especially when scrolling TUTORIAL.ja on a
frame that uses the xft font backend. I also observe the increase of
the total number of xftfont_draw calls, and a string in a single font
and color, which was originally displayed by one call, is now
unnecessarily divided into smaller units.
As an experiment, I tried restoring the following change, and then the
performance became comparable to 23.1.
2009-11-17 Jan Djärv <jan.h.d@swipnet.se>
* font.c (font_open_entity): Do not use cache, it does not pick up new
fontconfig settings like hinting.
*** 2975,2985 ****
--- 2987,3001 ----
else if (CONSP (Vface_font_rescale_alist))
scaled_pixel_size = pixel_size * font_rescale_ratio (entity);
+ #if 0
+ /* This doesn't work if you have changed hinting or any other parameter.
+ We need to make a new object in every case to be sure. */
for (objlist = AREF (entity, FONT_OBJLIST_INDEX); CONSP (objlist);
objlist = XCDR (objlist))
if (! NILP (AREF (XCAR (objlist), FONT_TYPE_INDEX))
&& XFONT_OBJECT (XCAR (objlist))->pixel_size == pixel_size)
return XCAR (objlist);
+ #endif
val = AREF (entity, FONT_TYPE_INDEX);
for (driver_list = f->font_driver_list;
The added comment implies that the simple removal of #if 0 causes
another problem for some cases, but I think creating a new font object
for each call is too much for the usual cases. Perhaps this part
needs some improvement.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next reply other threads:[~2009-12-17 2:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 2:49 YAMAMOTO Mitsuharu [this message]
2009-12-17 7:39 ` Display performance degradation Jan D.
2009-12-17 20:08 ` Eli Zaretskii
2009-12-18 16:47 ` Jan Djärv
2009-12-18 21:20 ` Eli Zaretskii
2010-01-02 11:05 ` Jan Djärv
2010-01-02 11:21 ` Eli Zaretskii
2010-01-02 14:31 ` Jan Djärv
2009-12-17 12:24 ` Kenichi Handa
2009-12-17 14:43 ` Chong Yidong
2009-12-18 3:53 ` Miles Bader
2009-12-17 16:42 ` Jan Djärv
2009-12-18 3:06 ` YAMAMOTO Mitsuharu
2009-12-18 5:46 ` Kenichi Handa
2009-12-19 2:56 ` YAMAMOTO Mitsuharu
2009-12-19 10:00 ` Andreas Schwab
2009-12-20 6:27 ` YAMAMOTO Mitsuharu
2009-12-21 1:17 ` Kenichi Handa
2009-12-21 2:11 ` Miles Bader
2009-12-21 2:31 ` Lennart Borgman
2009-12-21 3:05 ` Miles Bader
2009-12-21 3:08 ` Lennart Borgman
2009-12-21 3:44 ` Miles Bader
2009-12-21 3:54 ` Lennart Borgman
2009-12-21 4:16 ` Miles Bader
2009-12-21 4:18 ` Lennart Borgman
2010-01-06 19:46 ` Jan Djärv
2010-01-07 8:26 ` YAMAMOTO Mitsuharu
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=wlmy1iuxgi.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=emacs-devel@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).