all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: eric@ericabrahamsen.net, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: async Gnus
Date: Wed, 26 Jan 2022 10:32:26 -0500	[thread overview]
Message-ID: <m38rv2fr79.fsf@fitzsim.org> (raw)
In-Reply-To: <871r0umtm1.fsf@elite.giraud> (Manuel Giraud's message of "Wed, 26 Jan 2022 15:58:30 +0100")

Hi Manuel,

Manuel Giraud <manuel@ledu-giraud.fr> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Manuel Giraud <manuel@ledu-giraud.fr>
>>> Date: Wed, 26 Jan 2022 11:05:43 +0100
>>> Cc: emacs-devel@gnu.org
>>> 
>>> I'm suprprise: I thought that `make-thread' create a proper system
>>> thread.
>>
>> It does.  But we only let a single thread at a time to run the Lisp
>> interpreter.  So if your thread runs a lot of Lisp, it will preempt
>> the main thread, and that means unresponsive Emacs.
>
> Ok so, as Python, Emacs has a GIL. As Gnus seems to be an heavy user of
> Lisp maybe my goal is inaccessible… I'll try to see what I end up with
> anyway 😅

Bug 49065 has a huge patch that, among other things, introduces a
background thread for gnus-group-get-new-news.  It was never accepted
because the author didn't break the larger patch into smaller chunks for
review.  Maybe you could start from that large patch, confirm the
asynchronous changes work for you, then separate out the
background-thread parts to submit.

Thomas



  reply	other threads:[~2022-01-26 15:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 16:58 async Gnus Manuel Giraud
2022-01-25 17:29 ` Eric Abrahamsen
2022-01-26 10:05   ` Manuel Giraud
2022-01-26 13:10     ` Eli Zaretskii
2022-01-26 14:58       ` Manuel Giraud
2022-01-26 15:32         ` Thomas Fitzsimmons [this message]
2022-01-26 16:36           ` Manuel Giraud
2022-01-26 17:53             ` Eric Abrahamsen
2022-02-01 16:26               ` Manuel Giraud

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=m38rv2fr79.fsf@fitzsim.org \
    --to=fitzsim@fitzsim.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=manuel@ledu-giraud.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.