unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Uberti via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>, 54608@debbugs.gnu.org
Subject: bug#54608: 29.0.50; xref-search-program-alist: support ugrep
Date: Mon, 28 Mar 2022 17:43:57 +0200	[thread overview]
Message-ID: <65a3c15a-d4e3-5a41-a237-3d1149407967@inventati.org> (raw)
In-Reply-To: <ab1ffb2d-a98d-3732-f630-59012bf17942@yandex.ru>

On 28/03/22 17:02, Dmitry Gutov wrote:
 > 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.

I tried `(benchmark-run (project-find-regexp "torvalds"))` in the Linux kernel code.

With grep: (3.628388951 6 0.3137041489999959)
With ugrep: (2.664314312 6 0.31696058299999663)

-- 
Manuel Uberti
www.manueluberti.eu





  reply	other threads:[~2022-03-28 15:43 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
2022-03-28 15:43       ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=65a3c15a-d4e3-5a41-a237-3d1149407967@inventati.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54608@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --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).