From: Eli Zaretskii <eliz@gnu.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: larsi@gnus.org, 8890@debbugs.gnu.org
Subject: bug#8890: 23.3; message writing slows emacs
Date: Sun, 11 Sep 2011 07:20:53 -0400 [thread overview]
Message-ID: <E1R2i5l-0007zR-VI@fencepost.gnu.org> (raw)
In-Reply-To: <m2ehznnyr0.fsf@pluto.luannocracy.com> (message from Dave Abrahams on Sun, 11 Sep 2011 06:45:39 -0400)
> From: Dave Abrahams <dave@boostpro.com>
> Cc: larsi@gnus.org, 8890@debbugs.gnu.org
> Date: Sun, 11 Sep 2011 06:45:39 -0400
>
> If you're just updating percentage complete, please don't do
> it more than once every .5 seconds... at the fastest!
Agreed, but that's something for the application programmers to
consider, not for the infrastructure.
> > Redisplay always slows down, but on any modern machine displaying only
> > the echo area should take a few milliseconds at the most, so I'd be
> > surprised if some real slowdown was involved.
>
> Don't forget that messages also fill up the *Messages* buffer.
I think that's so fast it can be ignored, unless _generating_ these
messages takes non-trivial computations.
> > Anyway, can you describe the situation in which you see these flashing
> > messages? The only one I can think of is when Emacs starts up and
> > restores a previous session. Is that your use case, or did you see
> > this in other situations?
>
> Yeah, there's something in Gnus, perhaps article expiry, that seems slow
> mostly because gnus-verbose defaults to 7 and it writes out gobs of
> messages. When I turned gnus-verbose down it seemed a lot faster.
Maybe there's something specific to Gnus, then. In which case it's a
good thing we have Lars listening ;-)
next prev parent reply other threads:[~2011-09-11 11:20 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1R2i5l-0007zR-VI@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=8890@debbugs.gnu.org \
--cc=dave@boostpro.com \
--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 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.