unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jacob Keller <jacob.e.keller@intel.com>, meta@public-inbox.org
Subject: Re: search by whole thread?
Date: Wed, 12 Apr 2023 20:17:42 +0000	[thread overview]
Message-ID: <20230412201743.M20097@dcvr> (raw)
In-Reply-To: <20230412-vividness-expectant-b3c889@meerkat>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Wed, Apr 12, 2023 at 12:06:53AM +0000, Eric Wong wrote:
> > I think the reason it's rare in MUAs is that it's potentially
> > very expensive.  But I think the `thread:{subquery}' feature
> > from notmuch I discussed with Konstantin the other week[1] can
> > do what you want it to do.
> > 
> > Keep in mind, notmuch-search-terms(7) states:
> > 
> > 	The performance of such queries can vary wildly.
> > 
> > And that's for a private client tool for a single user.
> 
> Yes, when I was wondering about that, it was really for the lei side of
> things. I don't really want to run expensive queries on lore (though I'm okay
> if we can turn it off for /all/ or other very large lists).

I expect relying on timeouts in an external process will be fine
for lore, especially since some expensive queries are already
possible :x

I suppose ITIMER_REAL is better than RLIMIT_CPU since the former
accounts for I/O time.  Xapian makes a lot of small pread
syscalls so I don't see it being stuck in D-state long on SSDs.

  reply	other threads:[~2023-04-12 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 22:59 search by whole thread? Jacob Keller
2023-04-12  0:06 ` Eric Wong
2023-04-12 18:29   ` Jacob Keller
2023-04-12 18:49   ` Konstantin Ryabitsev
2023-04-12 20:17     ` Eric Wong [this message]
2023-04-12 21:01       ` Jacob Keller
2023-04-12 21:21         ` Eric Wong

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=20230412201743.M20097@dcvr \
    --to=e@80x24.org \
    --cc=jacob.e.keller@intel.com \
    --cc=konstantin@linuxfoundation.org \
    --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.
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).