From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Sven Joachim <svenjoac@gmx.de>
Cc: bugs@gnus.org, ding@gnus.org
Subject: Re: Huge memory consumption on accessing large newsgroup
Date: Fri, 10 Aug 2007 18:08:10 +0900 [thread overview]
Message-ID: <b4m3ayriwp1.fsf@jpl.org> (raw)
In-Reply-To: <87wsw4u21m.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
(I added the ding list to Cc.)
>>>>> Sven Joachim wrote:
> Gnus v5.11
> GNU Emacs 22.1.50.1 (i486-pc-linux-gnu, GTK+ Version 2.10.13)
> of 2007-08-06 on debian, modified by Debian
> 200 news.motzarella.org InterNetNews NNRP server INN 2.4.4 (20060818 snapshot) ready (posting ok).
I visited http://news.motzarella.org/ and got an account on
Motzarella out of curiosity. ;-)
> When accessing comp.os.linux.misc on news.motzarella.org, a _very_
> large newsgroup with more than 30,000,000 articles, Emacs' memory
> footprint grew heavily.
Yes, now the ACTIVE of that group is:
[-- Attachment #2: Type: application/emacs-lisp, Size: 73 bytes --]
[-- Attachment #3: Type: text/plain, Size: 759 bytes --]
However, I verified there are actually no more than less than
3,000 articles. It should not be a cause of this problem.
> It took ~2 minutes to display its question
> "How many articles...?" and the memory usage was at 555 MB (RSS).
> When I answered "500" and the summary buffer finally appeared, it grew
> up to 893 MB. Which is a bit scary, since my computer has "only" 1 GB
> of RAM and is now already paging quite a bit.
> Will this become better if I subscribe to the newsgroup and catch up?
> In any case I probably will have to kill my current Emacs session soon.
The real cause is that Gnus first expands this ACTIVE data into:
(3437 3438 3439 3440 ...... 30538696 30538697 30538698 30538699)
If you run Emacs on a super computer, try this:
[-- Attachment #4: Type: application/emacs-lisp, Size: 43 bytes --]
[-- Attachment #5: Type: text/plain, Size: 116 bytes --]
I think the possible solution is to narrow the range into the
one with which Emacs can work lightly. Here it is:
[-- Attachment #6: Type: application/emacs-lisp, Size: 183 bytes --]
[-- Attachment #7: Type: text/plain, Size: 576 bytes --]
The 10000 will probably need to be a customizable variable. I'm
going to do it next week.
BTW, I needed to set the server variable `nntp-authinfo-force'
to t in order to let No Gnus v0.7 send the AUTHINFO data to the
Motzarella server as follows:
(nntp "motzarella"
(nntp-address "news.motzarella.org")
(nntp-authinfo-user "yamaoka")
(nntp-authinfo-password "********")
(nntp-authinfo-force t)
...)
I guess you have the FORCE element in the ~/.authinfo file since
such a server variable has not been implemented yet in Gnus v5.11.
Regards,
next parent reply other threads:[~2007-08-10 9:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wsw4u21m.fsf@gmx.de>
2007-08-10 9:08 ` Katsumi Yamaoka [this message]
2007-08-10 11:39 ` Katsumi Yamaoka
2007-08-10 12:43 ` Sven Joachim
2007-08-13 11:44 ` Katsumi Yamaoka
2007-08-13 17:30 ` Sven Joachim
2007-08-14 11:46 ` Katsumi Yamaoka
2007-09-13 10:27 ` Katsumi Yamaoka
2007-08-10 12:42 ` Sven Joachim
2007-09-29 21:04 ` Gaute Strokkenes
2007-09-30 22:11 ` Ted Zlatanov
2007-10-01 0:29 ` Katsumi Yamaoka
2007-10-01 1:04 ` Daniel Pittman
2007-10-02 2:13 ` Ted Zlatanov
2007-10-02 3:23 ` Daniel Pittman
2007-10-02 11:11 ` Ted Zlatanov
2007-10-02 12:17 ` Daniel Pittman
2007-10-02 16:08 ` Ted Zlatanov
2007-10-03 0:19 ` Daniel Pittman
2007-10-02 13:33 ` Daniel Pittman
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=b4m3ayriwp1.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=bugs@gnus.org \
--cc=ding@gnus.org \
--cc=svenjoac@gmx.de \
/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).