Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Husain Alshehhi" <husain@alshehhi.io>
To: info-gnus-english@gnu.org
Subject: Re: Inhibiting gnus-get-new-news at startup
Date: Tue, 02 Jan 2024 21:34:32 -0600	[thread overview]
Message-ID: <87cyujxf7b.fsf@> (raw)
In-Reply-To: <47073.0785092869$1703954497@news.gmane.org> (Husain Alshehhi's message of "Sat, 30 Dec 2023 10:41:06 -0600")


I might have spoken too soon. It appears that the issue is not with nntp
groups, but with nnrss. I ran the profile and saw the following:

        2999  73% - command-execute
        2641  64%  - funcall-interactively
        2637  64%   - gnus
        2637  64%    - gnus-1
        2626  63%     - #<compiled 0xffd5eb68ee5dbf1>
        2626  63%      - gnus-setup-news
        2622  63%       - gnus-get-unread-articles
        2403  58%        - gnus-read-active-for-groups
        1855  45%         - gnus-read-active-file-2
        1855  45%          - gnus-retrieve-groups
        1855  45%           - nnrss-retrieve-groups
        1652  40%            - nnrss-check-group
        1356  33%             - nnrss-fetch
        1288  31%              - xml-parse-region
        1288  31%               - xml--parse-buffer
        1288  31%                - xml-parse-tag-1
        1288  31%                 - xml-parse-tag-1
        1288  31%                  - xml-parse-tag-1
        1284  31%                   - xml-parse-tag-1
        1221  29%                    - xml-parse-tag-1
         153   3%                     - xml-parse-string
          15   0%                        #<compiled 0xa4190491901ef>
          16   0%              + mm-url-insert
         259   6%             + nnrss-make-hash-index
          15   0%             + nnrss-find-el
           4   0%               nnrss-translate-file-chars
           3   0%             + nnrss-get-namespace-prefix
         199   4%            + nnrss-possibly-change-group
         544  13%         - gnus-request-scan
         544  13%          - nnmaildir-request-scan
         541  13%           - nnmaildir--scan
         431  10%            - nnmaildir--grp-add-art
         401   9%             - nnmaildir--update-nov
         141   3%              + nnheader-insert-file-contents
           7   0%              + nnmaildir--param
          21   0%            + mapcar
           4   0%         + gnus-finish-retrieve-group-infos
         162   3%        + gnus-open-server
          40   0%        + gnus-request-update-info
          14   0%        + gnus-retrieve-group-data-early
           3   0%          gnus-message
           4   0%       + gnus-cache-open
           7   0%     + gnus-splash
           4   0%     + gnus-read-init-file
           4   0%   + execute-extended-command
         358   8%  + byte-code
        1107  26% - ...
        1107  26%    Automatic GC

It appears that much of the time was spent on fetching and parsing rss
feeds. I am using (setq nnrss-use-local t) which I expected to be much
faster, but that gnus is still very slow.

Some of you suggested to change the level of subscription to a higher
number. What are the implications of this change? I mainly am interested
in getting the list of new news of all subscribed groups about once a
day.


  parent reply	other threads:[~2024-01-03  3:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47073.0785092869$1703954497@news.gmane.org>
2023-12-30 19:01 ` Eric Abrahamsen
2023-12-31  3:38 ` Emanuel Berg
2023-12-31 23:27 ` Inhibiting gnus-get-new-news at startup, Re: Inhibiting gnus-get-new-news at startup, " James Thomas
2024-01-01  3:39   ` Eric Abrahamsen
2024-01-02  0:48   ` Dan Christensen
2024-01-02  2:35     ` Bob Newell
2024-01-03  3:34 ` Husain Alshehhi [this message]
     [not found] ` <30352.9598562577$1704252905@news.gmane.org>
2024-01-03 12:09   ` Eric S Fraga
2024-01-03 15:23     ` Eric Abrahamsen
2024-01-03 16:06       ` Eric S Fraga
2023-12-30 16:41 Husain Alshehhi
2023-12-30 17:06 ` Bartosz Kaczyński
2024-01-04 10:01 ` Lars-Johan Liman
2024-01-04 13:55   ` Eric S Fraga
2024-01-06  8:13     ` Lars-Johan Liman
2024-01-06 15:56       ` Eric S Fraga
2024-01-07 10:22         ` Lars-Johan Liman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cyujxf7b.fsf@ \
    --to=husain@alshehhi.io \
    --cc=info-gnus-english@gnu.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 NNTP newsgroup(s).