From: Eric Wong <e@80x24.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: meta@public-inbox.org
Subject: Re: Searching via git grep?
Date: Fri, 20 Jul 2018 06:11:07 +0000 [thread overview]
Message-ID: <20180720061106.4f2u2zpdxnsilrxt@dcvr> (raw)
In-Reply-To: <87601adfo7.fsf@xmission.com>
"Eric W. Biederman" <ebiederm@xmission.com> wrote:
> My current goal is to make it pleasant to read linux-kernel and possibly
> other large archives on my personal machine. Right now the git
> trees for linux-kernel are aboug 6.8G. Small enough to fit in RAM.
>
> The Xapian indexes are about 63G. Not small enough to fit in ram.
> They are also not fast to update when I pull in a new batch of messages
> from linux-kernel.
Interesting, how long does it take to do an incremental index
medium/full for you? Setting XAPIAN_FLUSH_THRESHOLD after my
patch yesterday should help noticeably, especially if you're on
HDD.
> So I am looking at using git grep as a stand-in for the Xapian indexes
> when indexlevel eq 'basic'.
>
> Given my personal ratio of searches to indexing I think I will save
> time in doing that. I don't have it all wired up yet to know if it will
> work well, but I suspect it will.
Totally understandable, and yes, if you can fit the LKML repos
into RAM it should be usable enough for a single user.
"git grep" also has the advantage of being able to use regexps,
which isn't possible with Xapian at the moment.
> Is it only the web interface where the advanced search functionality is
> available?
Yes. I don't think there's a good way to implement search for
NNTP on the server side... IMAP has specs for implementing
search; but I don't know how much overlap there is with what
our web UI currently offers.
next prev parent reply other threads:[~2018-07-20 6:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 20:47 Searching via git grep? Eric W. Biederman
2018-07-19 21:12 ` Eric Wong
2018-07-19 22:27 ` Eric W. Biederman
2018-07-20 6:11 ` Eric Wong [this message]
2018-07-20 12:37 ` Eric W. Biederman
2018-07-20 23:56 ` Eric W. Biederman
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180720061106.4f2u2zpdxnsilrxt@dcvr \
--to=e@80x24.org \
--cc=ebiederm@xmission.com \
--cc=meta@public-inbox.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://80x24.org/public-inbox.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).