From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: asjo@koldfront.dk, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Rendering regression in Gnus with gnus-treat-from-gravatar
Date: Wed, 15 Apr 2020 15:01:49 +0300 [thread overview]
Message-ID: <83blntgdoy.fsf@gnu.org> (raw)
In-Reply-To: <m2k12hj73k.fsf@gmail.com> (message from Robert Pluim on Wed, 15 Apr 2020 13:55:59 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: asjo@koldfront.dk, ding@gnus.org, emacs-devel@gnu.org
> Date: Wed, 15 Apr 2020 13:55:59 +0200
>
> Eli> The thread will not run until the main thread yields in some way.
> Eli> What does the main thread do after calling make-thread?
>
> (with-mutex gravatar-mutex
> (setq gravatar-retrieve-params
> (list mail-address callback cbargs))
> (condition-notify gravatar-cond-var))
> (thread-yield)
>
> where the gravatar thread is doing 'condition-wait' on that same
> condition var. Except that it then fires off an asynchronous url
> request, so perhaps thatʼs the slow bit.
You could put a breakpoint before and after the URL request, and then
see which part takes time.
> Or itʼs the interaction with redisplay thatʼs slow
What interaction is that?
next prev parent reply other threads:[~2020-04-25 17:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877dym5fes.fsf@tullinup.koldfront.dk>
2020-04-11 14:15 ` Robert Pluim
2020-04-11 15:16 ` Adam Sjøgren
2020-04-11 16:53 ` Robert Pluim
2020-04-14 13:14 ` Robert Pluim
2020-04-14 15:46 ` Eli Zaretskii
2020-04-14 17:32 ` Adam Sjøgren
2020-04-15 8:15 ` Robert Pluim
2020-04-15 9:41 ` Eli Zaretskii
2020-04-15 10:13 ` Robert Pluim
2020-04-15 11:38 ` Eli Zaretskii
2020-04-15 11:55 ` Robert Pluim
2020-04-15 12:01 ` Eli Zaretskii [this message]
2020-04-15 13:54 ` Robert Pluim
2020-04-15 14:12 ` Eli Zaretskii
2020-04-15 14:20 ` Robert Pluim
2020-04-22 14:25 ` Tassilo Horn
2020-04-22 14:39 ` Tassilo Horn
2020-04-22 14:56 ` Robert Pluim
2020-04-22 17:32 ` Tassilo Horn
2020-04-22 14:59 ` Robert Pluim
2020-04-22 17:01 ` Tassilo Horn
2020-04-22 17:23 ` Robert Pluim
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=83blntgdoy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=asjo@koldfront.dk \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@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.
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 NNTP newsgroup(s).