unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Analysis of redisplay performance on Windows
Date: Sun, 27 Jul 2008 17:40:12 -0400	[thread overview]
Message-ID: <87iqurhupv.fsf@stupidchicken.com> (raw)
In-Reply-To: <488CE8F6.5080001@gnu.org> (Jason Rumney's message of "Sun, 27 Jul 2008 22:30:30 +0100")

Jason Rumney <jasonr@gnu.org> writes:

> Chong Yidong wrote:
>
>> Could you verify that setting the overlaps argument unconditionally to 1
>> in draw_glyphs indeed removes the performance problem?  If so, we can
>> work around this.
>
> Doing this results in a blank frame.  #if 0 around the block that calls
> left_overwritten and right_overwritten does not solve the performance
> problems completely (redisplay can still not keep up with scrolling,
> whereas Emacs 22 can on the same PC), and without that code, the display
> becomes garbaged, so I don't think it is worth pursuing this workaround.

I wasn't suggesting this as a final solution, just as a starting point
to look for the solution.

What you wrote seems to imply that left_overwritten and
right_overwritten aren't really the problem; they have a performance
impact simply because they cause more glyphs to be drawn (i.e., for
redrawing overwritten glyphs).  But the ultimate problem is that drawing
glyphs is a much slower operation, compared to GNU/Linux.  The question
is, what's the reason for this slowness, and can we fix it?




  reply	other threads:[~2008-07-27 21:40 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 [this message]
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
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=87iqurhupv.fsf@stupidchicken.com \
    --to=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).