[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [leafnode-list] 2.0b8_ma3 leafnode very slow

Stefan Wiens <s.wi@xxxxxxx> writes:

> > Well, I looked again, after my initial reply, and found that on my
> > machine, leafnode was operating in line-buffered mode, for whatever
> > reason (it did not request that). 
> Does it indeed see isatty(1)!=0?

I didn't check, leafnode itself does not reference isatty().

> With 2.0b8, I can see no significant difference between line-buffered
> and full-buffered mode, no matter if connected directly to a terminal
> or to a socket (Nagle algorithm), besides slightly increased CPU
> usage.

Fully-buffered is quicker with Gnus here. Sure, verbosity counts as
well, but "slightly increased CPU usage" can be avoided, so should it be

> Another possible reason for slow XOVER response:
> There is a significant overhead when executing findxover() with
> debug>0. There is an IMHO unnecessary check for correct ordering,
> which might better be done when parsing the .overview file, making
> qsort() unnecessary in most cases.

qsort should not be the bottleneck.

Matthias Andree

leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list