unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: Multithread or multiprocess in emacs??
Date: Mon, 17 Apr 2023 13:37:41 +0000	[thread overview]
Message-ID: <87354yiq8q.fsf@posteo.net> (raw)
In-Reply-To: <7w4yjuxtu6rm325oeddtl3fu4oe64fsarru3s4fnh7on5m7udl@wzxqo5pm6es7> (Ergus's message of "Sun, 16 Apr 2023 22:50:24 +0200")

Ergus <spacibba@aol.com> writes:

> Hi:
>
> Very recently I have seen a code in an elpa package that starts async
> subprocesses; but instead of using make-process the package uses
> make-thread + process-file. This was to reduce the latency and some
> lagging (not evident in my system, but apparently it annoyed the
> package's author).
>
> So, my question is now: Has anyone measured the overhead created by
> make-process in critical parts of the code like flymake checkers, or
> ispell? and compared with creating new threads?
>
> If this is somehow significant maybe we may consider adding a helper
> thread or thread-pool for some purposes as now the C11 standard has the
> threads.h header.

Note that C11 threads are controversial[0], but also optional.  Also, I
might be mistaken, but shouldn't Pthreads in some form be available on
platforms that Emacs runs on?  Also, see (elisp) C Dialect.

There was an article[1] on the topic last year, which might be helpful.

[0] https://gustedt.wordpress.com/2012/10/14/c11-defects-c-threads-are-not-realizable-with-posix-threads/
[1] https://coredumped.dev/2022/05/19/a-vision-of-a-multi-threaded-emacs/.

> Is there any work already in this direction? How does Elisp handles
> multithreading?
>
> Best,
> Ergus



  parent reply	other threads:[~2023-04-17 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7w4yjuxtu6rm325oeddtl3fu4oe64fsarru3s4fnh7on5m7udl.ref@wzxqo5pm6es7>
2023-04-16 20:50 ` Multithread or multiprocess in emacs?? Ergus
2023-04-17  2:26   ` Eli Zaretskii
2023-04-17 13:37   ` Philip Kaludercic [this message]
2023-04-17 13:58     ` Po Lu

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=87354yiq8q.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.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.
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).