From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Peter Münster" <pmlists@free.fr>
Cc: 25197@debbugs.gnu.org
Subject: bug#25197: 26.0.50; notifications-notify is extremely slow with double buffering
Date: Fri, 03 Sep 2021 10:55:44 +0200 [thread overview]
Message-ID: <87v93iyr5b.fsf@gnus.org> (raw)
In-Reply-To: <87wpf3v3io.fsf@roche-blanche.net> ("Peter Münster"'s message of "Tue, 13 Dec 2016 23:59:59 +0100")
Peter Münster <pmlists@free.fr> writes:
> notifications-notify is extremely slow, when the notification windows
> overlap the emacs window.
>
> Command for testing:
>
> time src/emacs -g 300x100 -Q --eval "(progn (require 'notifications)
> (dotimes (i 20) (notifications-notify :title \"TEST\"))
> (kill-emacs))"
>
> Result before the commit:
>
> real 0m1.820s
> user 0m0.668s
> sys 0m0.060s
>
> Result after the commit:
>
> real 0m11.782s
> user 0m0.636s
> sys 0m0.128s
>
> "-g 300x100" or something similar is needed, to get a nearly full-screen
> window, so that the notifications overlap the emacs window.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I tried reproducing this in Emacs 28 with various -g sizes, and I can't
see any particular slowness here:
real 0m0.334s
user 0m0.145s
sys 0m0.028s
Are you still seeing this issue in recent Emacs versions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-03 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 22:59 bug#25197: 26.0.50; notifications-notify is extremely slow Peter Münster
2017-09-02 12:15 ` Eli Zaretskii
2017-09-03 10:51 ` Peter Münster
2021-09-03 8:55 ` Lars Ingebrigtsen [this message]
2021-09-06 20:21 ` bug#25197: 26.0.50; notifications-notify is extremely slow with double buffering Peter Münster
2021-09-07 5:33 ` Eli Zaretskii
2021-09-07 13:19 ` Peter Münster
2021-09-14 15:58 ` Peter Münster
2021-09-15 8:01 ` Lars Ingebrigtsen
2021-09-15 12:24 ` Peter Münster
2021-09-16 12:23 ` Lars Ingebrigtsen
2021-09-16 13:56 ` Peter Münster
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=87v93iyr5b.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=25197@debbugs.gnu.org \
--cc=pmlists@free.fr \
/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.