unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 8890@debbugs.gnu.org
Subject: bug#8890: 23.3; message writing slows emacs
Date: Thu, 15 Sep 2011 22:22:45 -0400	[thread overview]
Message-ID: <m2litpp6oa.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <m2mxeb11ac.fsf@boostpro.com> (Dave Abrahams's message of "Sun, 11 Sep 2011 12:39:23 -0400")


on Sun Sep 11 2011, Dave Abrahams <dave-AT-boostpro.com> wrote:

> on Sun Sep 11 2011, Eli Zaretskii <eliz-AT-gnu.org> wrote:
>
>>> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
>>
>>> Cc: Eli Zaretskii <eliz@gnu.org>,  8890@debbugs.gnu.org
>>> Date: Sun, 11 Sep 2011 16:52:56 +0200
>>> 
>>> Emacs does clever screen updates, though.  So if the only thing that
>>> changes is the number before the percentage, Emacs won't repaint the
>>> entire line, I think?
>>
>> True.  Like I said, redisplay of the echo area is very fast.
>
> I don't think it's clever enough.  Try this:
> (let (timings)
>   (dolist (reps '(1 10))
>     (let ((start-time (current-time)))
>       (loop for x to 10000 do
>             (loop repeat reps do
>                   (message "message #%s" x)))
>       (push (time-subtract (current-time) start-time) timings)))
>   (message "%s" (mapcar 'time-to-seconds timings)))
> I get (29.539774 2.514761)
>
> I think this shows that it takes (more than) 10x as long to write out
> the same message 10 times as it does to write it out once.

<bump> 

The above looks to me like conclusive evidence that writing out the same
percentage many times as part of a progress indication, rather than,
say, updating progress information once per second, will slow things
down a lot... and that's not a Gnus-specific problem.  *I* think this is
important, anyway.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com





  reply	other threads:[~2011-09-16  2:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 16:45 bug#8890: 23.3; message writing slows emacs Dave Abrahams
2011-09-11  4:32 ` Lars Magne Ingebrigtsen
2011-09-11  6:54   ` Dave Abrahams
2011-09-11  8:55     ` Eli Zaretskii
2011-09-11 10:45       ` Dave Abrahams
2011-09-11 11:20         ` Eli Zaretskii
2011-09-11 11:30           ` Dave Abrahams
2011-09-11 14:52             ` Lars Magne Ingebrigtsen
2011-09-11 15:58               ` Eli Zaretskii
2011-09-11 16:39                 ` Dave Abrahams
2011-09-16  2:22                   ` Dave Abrahams [this message]
2011-09-16  8:54                   ` Eli Zaretskii
2011-09-11 14:51         ` Lars Magne Ingebrigtsen
2011-09-16 13:18 ` Stefan Monnier
2011-09-16 13:45   ` Eli Zaretskii
2011-09-16 14:20     ` Stefan Monnier
2011-09-16 15:11       ` Dave Abrahams
2011-09-17  5:19         ` Lars Magne Ingebrigtsen
2011-09-17  6:23           ` Dave Abrahams
2011-09-17  8:25           ` Eli Zaretskii
2011-09-17  8:29             ` Lars Magne Ingebrigtsen
2011-09-17  9:24               ` Eli Zaretskii
2011-09-17 12:01               ` Juri Linkov
2011-09-17 21:06           ` Stefan Monnier
2011-09-18  6:50             ` Lars Magne Ingebrigtsen
2011-09-18 13:16               ` Stefan Monnier
2011-09-21 19:01                 ` Lars Magne Ingebrigtsen
2022-04-26 13:20           ` Lars Ingebrigtsen
2011-09-16 15:09     ` Dave Abrahams

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=m2litpp6oa.fsf@pluto.luannocracy.com \
    --to=dave@boostpro.com \
    --cc=8890@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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).