Re: extreme cpu usage with nndir (on specific files)

[Harry Putnam <reader@newsguy.com>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> One way to find out what the heck Emacs is doing is to M-x
> toggle-debug-on-quit RET, then hit C-g when it takes the long time.
> Do this several times, and you might get an idea what takes so long.
> 
> Hm.
> 
> Or maybe M-x elp-instrument-package RET nndir RET?  Anybody out there
> who groks elp?

I found out a little by a different method.  First I stripped the 
`^#! rnews ' line replaced it with `From gnus@rnews'.  That didn't
help so it wasn't the header with the #!  causing the trouble.  Next I
stripped the Xref header.  That helped a lot so that header was
causing trouble.  Then I began to notice that gnus had created  a
number of messages from my archive with  `nobody' as sender and `no
subject'.

Checking those messages in the actual archive I found those particular
messages had the `From: ' line above the `Path: ' line.

Finally I made a small awk program that puts `X-' in front of:

X-#! rnews
X-Xref:
X-Path:

Adds my own Path: line with a blank line before it:

fix.awk:
---------
/^#! / {a=1}
/^$/ {a=0}
/^#! rnews/ && a=1 \
{print "\nPath: harrys.news.service!verygood!at.home.now\nX-"$0;next}
/^Xref: / && a=1 {print "X-"$0;next}
/^Path: / && a=1 {print "X-"$0;next}{print}

Gnus liked it... pulled the unsorted  complete archive in as a nndoc
and sorted it by date and copied to the desired nnml+n2m groups.

All handling of these files now take normal amounts of time and I was
able to preserver the original headers (sort of).

I think the main problem was the Xref: header.  Is that likely to give
gnus a problem?

This all took so long that I think I'll wait till next time to try the
approach you suggested.