unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Andrew Cohen <cohen@bu.edu>
Cc: 63842@debbugs.gnu.org, cohen@andy.bu.edu
Subject: bug#63842: 30.0.50; Slow 'gnus-summary-refer-thread'
Date: Sat, 03 Jun 2023 15:23:17 +0200	[thread overview]
Message-ID: <87ilc44r3u.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <87bkhxl9th.fsf@ust.hk> (Andrew Cohen's message of "Sat, 03 Jun 2023 07:32:26 +0800")

Andrew Cohen <cohen@bu.edu> writes:

[...]

> Can you tell me (for circumstances where the referral is slow):

Hi Andrew,

> 1. What kind of group and the backend used  in the group from which you
> did the referral (imap, nntp, etc)

I'm retrieving my mail via IMAP into a local nnml backend.  This is in
such group that I witness the slowdown.  I have not tested on any other
backend.

> 2. What search engine are you using (imap, notmuch, etc)

I have setup notmuch onto the default nnml directory and set
'gnus-select-method' as follow:
--8<---------------cut here---------------start------------->8---
(setq gnus-select-method '(nnml "" (gnus-search-engine gnus-search-notmuch)))
--8<---------------cut here---------------end--------------->8---

> 3. When the thread referral happens which groups are getting searched?
> (In particular, what is the value of
> 'gnus-refer-thread-use-search? And is the search on the full server or
> is it restricted to a single group?). And can you tell if the same set of
> groups is being searched before and after the slowdown appeared?

I have let 'gnus-refer-thread-use-search' to its default NIL value.  My
search was restricted to a single (mail) group and, previously, I was
doing the same thread referral search on the same group.

Thanks and hope this helps.
-- 
Manuel Giraud





  reply	other threads:[~2023-06-03 13:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 13:17 bug#63842: 30.0.50; Slow 'gnus-summary-refer-thread' Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-02 15:26 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-02 23:32 ` Andrew Cohen
2023-06-03 13:23   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-06-15  5:55     ` Eli Zaretskii
2023-06-15 17:59       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-16 10:36       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-16 23:37         ` Andrew Cohen
2023-06-17 22:16           ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-18  0:45             ` Andrew Cohen
2023-06-18 20:57               ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-19 12:58                 ` Andrew Cohen
2023-06-19 15:44                   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-23 10:00                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-01  8:25                       ` Eli Zaretskii
     [not found]                         ` <87edlsav34.fsf@ust.hk>
2023-07-01  9:49                           ` Eli Zaretskii

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=87ilc44r3u.fsf@ledu-giraud.fr \
    --to=bug-gnu-emacs@gnu.org \
    --cc=63842@debbugs.gnu.org \
    --cc=cohen@andy.bu.edu \
    --cc=cohen@bu.edu \
    --cc=manuel@ledu-giraud.fr \
    /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).