Re: How to reduce pickaxe times for a particular repo?

From: Pavel Rappo <pavel.rappo@gmail.com>
Date: Jun 28, 2022, 12:35 UTC
Message-ID: <CAChcVu=w8mxFtXHukZkf-VswchH_sRppCm=0XZbwh=9-Y4P8cg@mail.gmail.com>
In-Reply-To: <220628.86bkudf19g.gmgdl@evledraar.gmail.com>

On Tue, Jun 28, 2022 at 12:58 PM Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

<snip>

> But eventually you'll simply run into the regex engine being slow

Since I know very little about git internals, I was under a naive impression that a significant, if not comparable to that of regex, portion of pickaxe's time is spent on computing diffs between revisions. So I assumed that there was a way to pre-compute those diffs.

<snip>

>  2. Stick that into Lucene with trigram indexing, e.g. ElasticSearch
>     might make this easy.

<snip>

> For someone familiar with the tools involved that should be about a day
> to get to a rough hacky solution, it's mostly gluing existing OTS
> software together.

<snip>

I'll see what I can do with external systems. You see, I initially came from a similar repository exposed through OpenGrok. But I think that something was wrong with the index or query syntax because I couldn't find the things that I knew were there. I was able to secure a git repo that was close to that of OpenGrok as I found pickaxe to be robust albeit slow alternative for my searches.

Thanks for the suggestion.