From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Benchmarking Gnus
Date: Sun, 20 Jan 2002 00:28:49 +0100 [thread overview]
Message-ID: <m38zatly32.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <818zaw7vtb.fsf@zion.bpnetworks.com>
Ami Fischman <usenet@fischman.org> writes:
> Not quite a "benchmarking" issue, more concerned w/ speed/effeciency. I
> have several nntp servers I use (main one + several "vendor" servers for
> specific programs, like gnus). I noticed that since adding virtual groups
> (which contain groups from multiple servers) the same server will be opened
> several times in one 'g' operation.
[...]
> Opening nntp server on news.ISP.net...done
[...]
> Opening nnvirtual server on ^nntp\+news\.ISP\.net:comp\.dcom\.xdsl\|nntp\+news\.ISP\.net:comp\.dcom\.telecom.tech$...done
> Opening nntp server on news.ISP.net...done
[...]
> Opening nnvirtual server on ^nntp\+news\.ISP\.net:gnu\.emacs\.gnus\|nntp\+news\.gnus\.org:gnus\.ding$...done
> Opening nntp server on news.ISP.net...done
[...]
> You'll note that news.ISP.net is opened several times, as is news.gnus.org.
> This wouldn't bother me, except the "Opening nntp server on..." message
> always takes a few seconds to scroll by, making me think that opening the
> extra connection is taking time that needn't be taken (for instance, if the
> first connection were kept open, or else, if _before_ checking new news,
> gnus figured out all the info it needs to ask of each server, and do it at
> the same time).
This definitely sounds like a bug. Gnus is supposed to keep the
connections open and re-use them as needed. The most likely reason I
see for this not happening is that Gnus isn't able to recognize the
groups as coming from the same server.
What is the `G e' output on two of the component groups that are
included in the two different nnvirtual groups?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-01-19 23:28 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 2:12 Lars Magne Ingebrigtsen
2002-01-16 4:42 ` Russ Allbery
2002-01-19 23:25 ` Lars Magne Ingebrigtsen
2002-01-16 6:35 ` Jesper Harder
2002-01-19 23:25 ` Lars Magne Ingebrigtsen
2002-01-16 12:45 ` Simon Josefsson
2002-01-16 16:51 ` Josh Huber
2002-01-16 17:21 ` Karl Kleinpaste
2002-01-16 19:26 ` Steinar Bang
2002-01-17 2:06 ` Daniel Pittman
2002-01-17 17:04 ` Ami Fischman
2002-01-19 23:28 ` Lars Magne Ingebrigtsen [this message]
2002-01-20 19:11 ` Ami Fischman
2002-01-20 19:15 ` Lars Magne Ingebrigtsen
2002-01-20 20:05 ` Ami Fischman
2002-01-20 20:03 ` Lars Magne Ingebrigtsen
2002-01-20 20:33 ` Ami Fischman
2002-01-18 23:42 ` Jesper Harder
2002-01-19 11:38 ` Simon Josefsson
2002-01-27 0:30 Lars Magne Ingebrigtsen
2002-01-27 0:35 ` IPmonger
2002-01-27 0:45 ` Lars Magne Ingebrigtsen
2002-01-29 16:03 ` IPmonger
2002-01-30 8:53 ` Kai Großjohann
2002-01-30 16:42 ` IPmonger
2002-01-30 17:38 ` Kai Großjohann
2002-01-30 18:15 ` Lars Magne Ingebrigtsen
2002-01-30 18:42 ` Josh Huber
2002-02-04 23:35 ` IPmonger
2002-02-04 23:48 ` IPmonger
2002-02-04 23:57 ` Daniel Pittman
2002-01-30 22:02 ` Wes Hardaker
2002-01-30 22:09 ` IPmonger
2002-01-31 1:25 ` Wes Hardaker
2002-01-31 3:22 ` ShengHuo ZHU
2002-01-31 15:29 ` Wes Hardaker
2002-01-31 16:34 ` Steinar Bang
2002-01-31 16:54 ` Bjørn Mork
2002-01-31 20:50 ` Steinar Bang
2002-01-31 22:35 ` Bjørn Mork
2002-02-01 7:14 ` Steinar Bang
2002-02-01 9:17 ` Bjørn Mork
2002-02-01 10:00 ` Steinar Bang
2002-02-01 11:24 ` Bjørn Mork
2002-02-01 11:29 ` Simon Josefsson
2002-02-01 12:52 ` Steinar Bang
2002-02-01 13:40 ` Simon Josefsson
2002-02-01 14:12 ` Steinar Bang
2002-02-01 14:39 ` ShengHuo ZHU
2002-02-01 15:01 ` Simon Josefsson
2002-02-01 15:31 ` Steinar Bang
2002-02-01 14:59 ` Simon Josefsson
2002-02-01 15:18 ` Steinar Bang
2002-02-01 16:51 ` Wes Hardaker
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=m38zatly32.fsf@quimbies.gnus.org \
--to=larsi@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).