Discussion of development issues
> > Subject: [freenet-dev] Client apps limiting load in bad ways
> >
> > FMS does bad things to limit load: Rather than queueing every
> > key at MaxRetries=-1, it does all the scheduling itself,
>
> Freetalk and WoT can do -1 because we/I ca
On Thursday 09 April 2009 10:43:32 bo-le at web.de wrote:
> > -Urspr?ngliche Nachricht-
> > Von: "Matthew Toseland"
> > Gesendet: 09.04.09 00:28:48
> > An: Discussion of development issues
> > Betreff: [freenet-dev] Client apps limiting loa
On Thursday 09 April 2009 09:22:08 VolodyA! V Anarhist wrote:
> Matthew Toseland wrote:
> > FMS does bad things to limit load: Rather than queueing every key at
> > MaxRetries=-1, it does all the scheduling itself, doing simple ClientGet's
> > with no maxretries and no priority (hence prio 2), in
> -Original Message-
> From: devl-bounces at freenetproject.org
> [mailto:devl-bounces at freenetproject.org] On Behalf Of Matthew Toseland
> Sent: Thursday, April 09, 2009 12:28 AM
> To: Discussion of development issues
> Subject: [freenet-dev] Client apps limitin
> -Urspr?ngliche Nachricht-
> Von: "Matthew Toseland"
> Gesendet: 09.04.09 00:28:48
> An: Discussion of development issues
> Betreff: [freenet-dev] Client apps limiting load in bad ways
> FMS does bad things to limit load: Rather than queueing every key at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland wrote:
> FMS does bad things to limit load: Rather than queueing every key at
> MaxRetries=-1, it does all the scheduling itself, doing simple ClientGet's
> with no maxretries and no priority (hence prio 2), in order to enforce a
>
FMS does bad things to limit load: Rather than queueing every key at
MaxRetries=-1, it does all the scheduling itself, doing simple ClientGet's
with no maxretries and no priority (hence prio 2), in order to enforce a
maximum number of parallel requests. Other client apps probably do similar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland wrote:
FMS does bad things to limit load: Rather than queueing every key at
MaxRetries=-1, it does all the scheduling itself, doing simple ClientGet's
with no maxretries and no priority (hence prio 2), in order to enforce a
-Ursprüngliche Nachricht-
Von: Matthew Toseland t...@amphibian.dyndns.org
Gesendet: 09.04.09 00:28:48
An: Discussion of development issues devl@freenetproject.org
Betreff: [freenet-dev] Client apps limiting load in bad ways
FMS does bad things to limit load: Rather than queueing
-Original Message-
From: devl-boun...@freenetproject.org
[mailto:devl-boun...@freenetproject.org] On Behalf Of Matthew Toseland
Sent: Thursday, April 09, 2009 12:28 AM
To: Discussion of development issues
Subject: [freenet-dev] Client apps limiting load in bad ways
FMS does
On Thursday 09 April 2009 09:22:08 VolodyA! V Anarhist wrote:
Matthew Toseland wrote:
FMS does bad things to limit load: Rather than queueing every key at
MaxRetries=-1, it does all the scheduling itself, doing simple ClientGet's
with no maxretries and no priority (hence prio 2), in order
On Thursday 09 April 2009 10:43:32 bo...@web.de wrote:
-Ursprüngliche Nachricht-
Von: Matthew Toseland t...@amphibian.dyndns.org
Gesendet: 09.04.09 00:28:48
An: Discussion of development issues devl@freenetproject.org
Betreff: [freenet-dev] Client apps limiting load in bad ways
] Client apps limiting load in bad ways
FMS does bad things to limit load: Rather than queueing every
key at MaxRetries=-1, it does all the scheduling itself,
Freetalk and WoT can do -1 because we/I can patch them right now.
This can be done for any SSK/CHK URIs which the plugins know
FMS does bad things to limit load: Rather than queueing every key at
MaxRetries=-1, it does all the scheduling itself, doing simple ClientGet's
with no maxretries and no priority (hence prio 2), in order to enforce a
maximum number of parallel requests. Other client apps probably do similar
14 matches
Mail list logo
