unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Mauger <mmaug@yahoo.com>
Cc: spinuvit@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Deffering redisplay in COMINT
Date: Sun, 13 Jan 2013 18:46:06 +0200	[thread overview]
Message-ID: <83a9sdrpyp.fsf@gnu.org> (raw)
In-Reply-To: <1358064889.40573.YahooMailNeo@web160906.mail.bf1.yahoo.com>

> Date: Sun, 13 Jan 2013 00:14:49 -0800 (PST)
> From: Michael Mauger <mmaug@yahoo.com>
> Cc: Vitalie Spinu <spinuvit@gmail.com>, Emacs Devel <emacs-devel@gnu.org>
> 
> In each display environment I ran the tests with `truncate-lines' set to
> `t' and then with it set to`nil'. 

When it was non-nil, did you also disable auto-hscroll-mode?
Displaying an hscrolled windows disables redisplay optimizations, so
redisplay will be much slower (and it already is slow with such long
lines).

> The two obvious takeaways from this is that GUIs are slower, and
> truncate-lines set to non-nil can be painful.

That's almost trivial.

> I've been staring at numbers for the last three days so I'm getting
> a little cross-eyed.  Let me know if there is something more that
> would help you.

AFAIU, the profiles say that redisplay takes the lion's share of the
time, and the less you trigger redisplay, the faster Emacs is.  Is
that true?  If so, this, too, should be almost obvious, since
displaying long lines is notoriously slow in Emacs.

Once again, why don't you collect the text in a buffer that is not
displayed until you actually want to present it to the user?

Also, if the text is known to be 7-bit ASCII, try displaying it in a
unibyte buffer, that should be faster in Emacs 24.




  reply	other threads:[~2013-01-13 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07  1:08 Deffering redisplay in COMINT Michael Mauger
2012-12-25 11:09 ` Vitalie Spinu
2013-01-06  8:09   ` Michael Mauger
2013-01-08 18:19     ` Stefan Monnier
2013-01-11 14:40       ` Michael Mauger
2013-01-11 15:55         ` Stefan Monnier
2013-01-13  8:14           ` Michael Mauger
2013-01-13 16:46             ` Eli Zaretskii [this message]
2013-01-16 14:39             ` Stefan Monnier

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=83a9sdrpyp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mmaug@yahoo.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=spinuvit@gmail.com \
    /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).