From: Arthur Miller <arthur.miller@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Experiment with threads - no concurrency?
Date: Mon, 06 Sep 2021 18:40:46 +0200 [thread overview]
Message-ID: <AM9PR09MB49777D1D645B2706B1229F8496D29@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <83wnntr9i5.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 Sep 2021 18:47:46 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Arthur Miller <arthur.miller@live.com>
>> Date: Mon, 06 Sep 2021 16:35:04 +0200
>>
>> I did a little experiment today. I wanted to count frequency of Emacs functions
>> usage. So I started by indexing all functions and macros.
>>
>> Since it is kind of lot's of I/O and independent tasks to do, I thought threads
>> could come handy. However I see no difference from sequential code.
>
> You shouldn't. Emacs doesn't switch threads on just any I/O, it
> switches threads when it waits for input from subprocesses, network,
> and keyboard.
Allright, so in order to exploit I/O concurrency here, the only way is to start
another emacs process asynchronously? Could split file list I get from
directory-files-recursively into say 4 parts, and process files in 4
processes. Is there any benefit to use threads in that case?
Not that it is terribly important, it takes like 3 seconds to parse all files in
lisp dir sequentially, but now when I opened the question ...
next prev parent reply other threads:[~2021-09-06 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 14:35 Experiment with threads - no concurrency? Arthur Miller
2021-09-06 15:17 ` Stefan Monnier
2021-09-06 16:35 ` Arthur Miller
2021-09-06 17:31 ` Eli Zaretskii
2021-09-06 17:38 ` T.V Raman
2021-09-06 18:11 ` Arthur Miller
2021-09-06 15:47 ` Eli Zaretskii
2021-09-06 16:40 ` Arthur Miller [this message]
2021-09-06 17:33 ` Eli Zaretskii
2021-09-06 18:10 ` Arthur Miller
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=AM9PR09MB49777D1D645B2706B1229F8496D29@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.