From: Harry Putnam <reader@newsguy.com>
Subject: Re: two agent nits
Date: Thu, 04 Dec 2003 21:54:29 -0600 [thread overview]
Message-ID: <m3fzfzgbre.fsf@newsguy.com> (raw)
In-Reply-To: <iluhe0g0wu4.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 05 Dec 2003 04:25:55 +0100")
Simon Josefsson <jas@extundo.com> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>>> OOPs.. I got the notion somewhere it would be on by default.
>>>
>>>>> Is it necessary to delete all .agentview still.
>>>>
>>>> Perhaps, I did it on all groups. Perhaps I should have only done so
>>>> for a few and debug why it didn't work for others...
>>>
>>> I can report that it seems to be working as expected without having
>>> done anything to .agentview files. Once I set
>>> gnus-agent-consider-all-articles to t and ran Js... well gnus is
>>> still chewing up the inodes as I write.
>>
>> Simon, I'm seeing lots of time chewed up when running Js. Even
>> though I'm fairly close to up with newsfeed. That is, I may have
>> 100-200 messages counting all groups to download. But I see massive
>> amounts of time go by when running Js. Judging by the lack of
>> activity on my asdsl modem lights it doesn't seem to be conversing
>> with nntp server.
>>
>> Are you seeing any delays.
>
> Yup. It delays while saying "Fetching headers" but no headers are
> transfered over the network. I think it is simply processing the
> headers internally. I'm sure it can be optimized, profiling it with
> elp would be the first towards that. My results below, but doing M-x
> load RET gnus-agent.el RET first would probably have generated more
> information.
This looks pretty wild...
> gnus-point-at-eol 500918 3.1774099999 6.343...e-06
Simon, what is the syntax for running that profile? I couldn't get
even a remote clue from C-h f elp<spc><spc>. And was discouraged to
find that an `i' (index) search on `elp' in emacs info pages just
brings up lots of hits help `help'.
`s' search gives no hits on `[^h]elp-'
next prev parent reply other threads:[~2003-12-05 3:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 16:53 Simon Josefsson
2003-11-30 19:53 ` Harry Putnam
2003-11-30 20:18 ` Simon Josefsson
2003-12-01 3:13 ` Harry Putnam
2003-12-01 4:47 ` Kevin Greiner
2003-12-01 11:39 ` Simon Josefsson
2003-12-01 15:56 ` Kevin Greiner
2003-12-01 16:46 ` Simon Josefsson
2003-12-01 17:30 ` Kevin Greiner
2003-12-01 19:45 ` Simon Josefsson
2003-12-01 20:35 ` Harry Putnam
2003-12-02 3:02 ` Wes Hardaker
2003-12-02 6:01 ` Kevin Greiner
2003-12-02 17:40 ` Simon Josefsson
2003-12-03 21:47 ` Harry Putnam
2003-12-03 22:14 ` Simon Josefsson
2003-12-04 1:50 ` Harry Putnam
2003-12-04 2:29 ` Simon Josefsson
2003-12-04 5:54 ` Harry Putnam
2003-12-05 2:57 ` Harry Putnam
2003-12-05 3:25 ` Simon Josefsson
2003-12-05 3:54 ` Harry Putnam [this message]
2003-12-05 4:13 ` Simon Josefsson
2003-12-05 13:33 ` Harry Putnam
2003-12-02 20:35 ` Simon Josefsson
2003-12-02 22:28 ` Kevin Greiner
2003-12-01 12:30 ` Harry Putnam
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=m3fzfzgbre.fsf@newsguy.com \
--to=reader@newsguy.com \
/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).