-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Toad wrote: | On Fri, Nov 21, 2003 at 02:25:08PM -0600, Tom Kaitchuck wrote: | |>On Tuesday 18 November 2003 04:36 pm, Tracy R Reed wrote: |> |>>On Tue, Nov 18, 2003 at 09:18:51PM +0000, Jonathan Howard spake thusly: |>> |>>>I think freenet is suffering because it doesn't have key space |>>>specialisation. NGR is trying to route quickly, all un-overload are |>> |>>Yep. |>> |>> |>>>speed. Don't know how to kick start it out of the current state though. |>>>The only other way I can think of at the moment is nodes having |>>>(semi)strict self key space specialisation. |>> |>>I did this to my ds and it has slowly but surely been un-specializing. It |>>does no good if other nodes don't learn your nodes specialization and |>>route to it. I suggest we stop routing data to nodes in desperation. If |>>there isn't a pretty good probability that the node will have it or if the |>>data is not clearly in the nodes specialization don't route to it. I would |>>rather see a DNF than force some other node to de-specialize by forcing it |>>to look for my data. |> |>How are you measuring specialization? If you are looking at your data store |>than I would say you never were specialized. However ether way, you aren't |>now. So, yes, we should do whatever we can to encourage this. IE: |>non-alchemistic caching. non-alchemistic Query Rejection etc. |> |>I'm going to go out on a limb and claim that Freenet is not suffering from |>Load balancing problems. It is suffering for Load problems. If all nodes are |>overloaded, then no amount of QRing or backing off will solve the problem. It |>is entirely possible that clients are using more bandwidth than the network |>has. In order to fix this we need to address the client software. It is | | | Yeah, because nobody will ever use Freenet except in the ways we want, | and the suggestion that somebody might release a killer app after | freenet 1.0 that just happened to abuse the network slightly is | ridiculous. |
It might not be a bad idea just temporarily. If the Freenet network as a whole truly IS overloaded, this will temporarily solve the problem. Then the bugs in NGR (and elsewhere) can be worked out, and this issue can be revisited at a later time with a more permanent fix. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/vsS0hctESbvQ8ZwRApYoAJ9h1udPFzSW8UCH8hYFGFST6+QxBQCfX4vx PJfaZp33Wr1qnfTgOT8LDfg= =257M -----END PGP SIGNATURE-----
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
