[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [leafnode-list] 2.0b1 speed issues
On Sat, Oct 28, 2000 at 07:49:14PM +0100, phil hunt wrote:
> OK, I've attached a file which is the debug log resulting from slrn
> reading in a newsgroup (soc.history.what-if) from Leafnode.
>
> This took approx 10 seconds to process a newsgroup with 270 messages in
> it. (On a 300MHz K6-2).
> Oct 28 18:57:26 comuno leafnode[26780]: <XOVER
> Oct 28 18:57:26 comuno leafnode[26780]: >412 Use the GROUP command first
This is normal.
[slrn sends a GROUP command for every group it's subscribed to]
> Oct 28 18:57:28 comuno leafnode[26780]: <GROUP soc.history.what-if
Now we enter the group we want to read.
> Oct 28 18:57:28 comuno leafnode[26780]: >211 8138 2 72545 soc.history.what-if group selected
> Oct 28 18:57:28 comuno leafnode[26780]: <HEAD 72084
> Oct 28 18:57:28 comuno leafnode[26780]: >221 72084 <8tb7o7$vdj$1@xxxxxxxxxxxxxx> article retrieved - head follows
> Oct 28 18:57:28 comuno leafnode[26780]: <HEAD 72151
slrn requests the headers of all articles in the group. This is what
takes so long. I don't understand why slrn does this. It could
use the XOVER command instead. In fact, I just tried to reproduce
this here. My slrn (Slrn Version: 0.9.6.2 (Feb 7 2000 16:09:56)
S-Lang Library Version: 1.2.2) uses XOVER. I couldn't find an
option to force slrn to use XOVER, but I'm not expert as I use
tin normally. Anyway, this looks more like a problem on the
client side to me.
Regards,
Jo:rg
--
Fortune cookie of the day:
"It's not just a computer -- it's your ass."
-- Cal Keegan
--
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list