From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: dmitry@gutov.dev, 71094@debbugs.gnu.org, rgm@gnu.org,
sbaugh@janestreet.com
Subject: bug#71094: [PATCH] Prefer to run find and grep in parallel in rgrep
Date: Thu, 23 May 2024 07:46:12 +0300 [thread overview]
Message-ID: <86o78x5e5n.fsf@gnu.org> (raw)
In-Reply-To: <87le41bqvd.fsf@ledu-giraud.fr> (message from Manuel Giraud on Wed, 22 May 2024 21:15:02 +0200)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: dmitry@gutov.dev, sbaugh@janestreet.com, 71094@debbugs.gnu.org,
> rgm@gnu.org
> Date: Wed, 22 May 2024 21:15:02 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> [...]
>
> > Thanks, but we need the timings of the corresponding Emacs commands,
> > not the commands run from the shell prompt.
>
> Ok. What are those commands and how to timed them?
It's rgrep, AFAIU, according to the original report in this bug's
discussion. Dmitry, would you please show Manual the commands you
were running in your benchmarks?
> > Btw, are you sure that xargs or grep don't pay attention to the fact
> > that their output is redirected to the null device, and do nothing?
> > Some variants of these commands are known to use such a trick, AFAIR.
>
> I don't know.
OK, thanks.
next prev parent reply other threads:[~2024-05-23 4:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 14:35 bug#71094: [PATCH] Prefer to run find and grep in parallel in rgrep Spencer Baugh
2024-05-21 20:00 ` Dmitry Gutov
2024-05-22 11:59 ` Eli Zaretskii
2024-05-22 12:34 ` Dmitry Gutov
2024-05-22 13:50 ` Eli Zaretskii
2024-05-22 14:22 ` Dmitry Gutov
2024-05-22 14:42 ` Eli Zaretskii
2024-05-22 14:50 ` Dmitry Gutov
2024-05-22 15:26 ` Eli Zaretskii
2024-05-22 17:47 ` Dmitry Gutov
2024-05-22 18:21 ` Eli Zaretskii
2024-05-22 18:06 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-22 18:30 ` Eli Zaretskii
2024-05-22 19:15 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-23 4:46 ` Eli Zaretskii [this message]
2024-05-23 13:24 ` Dmitry Gutov
2024-05-24 17:44 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 15:57 ` Dmitry Gutov
2024-05-22 18:51 ` Dmitry Gutov
2024-05-22 19:36 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-22 19:59 ` Dmitry Gutov
2024-05-22 12:54 ` Spencer Baugh
2024-05-26 9:47 ` Eli Zaretskii
2024-05-30 12:29 ` Spencer Baugh
2024-05-30 14:52 ` Eli Zaretskii
2024-06-28 14:03 ` Spencer Baugh
2024-06-30 5:07 ` Stefan Kangas
2024-07-03 12:53 ` Spencer Baugh
2024-07-03 13:42 ` Andrea Corallo
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=86o78x5e5n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71094@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=manuel@ledu-giraud.fr \
--cc=rgm@gnu.org \
--cc=sbaugh@janestreet.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).