Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: News scan on startup vs 'g' in group buff
Date: Sat, 26 Oct 2013 18:41:31 -0400	[thread overview]
Message-ID: <87zjpvejtw.fsf@newsguy.com> (raw)
In-Reply-To: <87k3gzrhra.fsf@nowhere.org>

Glyn Millington <glyn.millington@gmail.com> writes:

>>> Have you tried passing a numerical argument to 'g' ?  ie 'C-u 2 g',
>>> if your mail groups are at level 2 and 1?
>>
>> No, I haven't keep different levels for yrs, and it would take some
>> serious rearranging to try that.
>
> The idea was to avoid a "hard" read of the active file, to see if that
> makes a difference. The right number will catch all your mail groups.
> If your mail groups are all level 4 or below then just do 'C-u 4 g'. If
> it seizes up again then no joy and you have lost a few more minutes, if
> not then the active file reading was the problem.

Is there no way to just watch the process and see what the heck gnus
is doing?  Where all the time is being spent?

All my groups are level 3, except nndrafts and its companion whos name
I forgot for the moment. Which are level 2.

I have dozens of nnml and nntp groups all level 3.

But, all may be fixed.  I just went thru a process of shedding 2
foreign servers.  An old defunct server for opera's newsgroups.  And a
server (apn forte-inc) that just ran out yesterday.

Even after deleting all the groups under both servers, I could not
kill them in server buffer.  Finally resorted to editing .newsrc.eld
by removing all references to either of those two servers.

After restart, I tried the 'g' in group buffer, and it worked just
fine.  It may have been a fluke and may be too soon to crow about it
but I think that cleanup has somehow fixed the problem.

I don't believe it could be the apn server since that just lapsed
today.  But possibly getting rid of the old opera server may have done
it. 

However, I'd still like to know how to watch the startup process (or
any other) and be able to see what calls are made etc.





  reply	other threads:[~2013-10-26 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 21:30 Harry Putnam
2013-10-22  6:54 ` Glyn Millington
2013-10-26 18:10   ` Harry Putnam
2013-10-26 18:47     ` Glyn Millington
2013-10-26 22:41       ` Harry Putnam [this message]
2013-10-27  6:28         ` Glyn Millington
2013-10-27 15:07           ` Harry Putnam
2013-10-29 23:58             ` Dan Christensen

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=87zjpvejtw.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=ding@gnus.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).