From: Dmitry Gutov <dgutov@yandex.ru>
To: Manuel Uberti <manuel.uberti@inventati.org>, 54608@debbugs.gnu.org
Subject: bug#54608: 29.0.50; xref-search-program-alist: support ugrep
Date: Mon, 28 Mar 2022 18:02:42 +0300 [thread overview]
Message-ID: <ab1ffb2d-a98d-3732-f630-59012bf17942@yandex.ru> (raw)
In-Reply-To: <7134959c-0a86-c997-bab4-376bdfa901c9@inventati.org>
On 28.03.2022 17:37, Manuel Uberti wrote:
> On 28/03/22 14:57, Dmitry Gutov wrote:
>> Does ugrep show better performance in this use case than grep on your
>> machine?
>
> With ugrep running `M-: (benchmark 100 (project-find-regexp
> "setq-default"))` in the directory containg Emacs source code returns:
>
> Elapsed time: 0.003903s
>
> With regular grep I get:
>
> Elapsed time: 0.026032s (0.022015s in 1 GCs)
0.026032s (0.022015s in 1 GCs) implies the total runtime sans GC
takes 0.026 - 0.022 = 0.004, which is pretty much the same as what you
measured for ugrep (0.0039). The the choice of search program is
unlikely to affect the GC time. It probably occurred randomly.
You might want to try doing a search in a larger project, for a
relatively unique string (which has less than 100 matches, say). Then
you can see the effect of search program's performance.
next prev parent reply other threads:[~2022-03-28 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 12:29 bug#54608: 29.0.50; xref-search-program-alist: support ugrep Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-28 12:57 ` Dmitry Gutov
[not found] ` <7134959c-0a86-c997-bab4-376bdfa901c9@inventati.org>
2022-03-28 15:02 ` Dmitry Gutov [this message]
2022-03-28 15:43 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-28 16:00 ` Dmitry Gutov
2022-03-28 16:05 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-31 8:58 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 1:35 ` Dmitry Gutov
2022-04-02 6:53 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=ab1ffb2d-a98d-3732-f630-59012bf17942@yandex.ru \
--to=dgutov@yandex.ru \
--cc=54608@debbugs.gnu.org \
--cc=manuel.uberti@inventati.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 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).