On Wednesday 13 August 2003 04:37 pm, Zooko wrote: > One potential problem with the way it does that is that it rests on the > assumption that true DNFs -- queries for data that is absent from Freenet > -- is evenly spread throughout the keyspace. I can imagine cases where > that assumption becomes untrue, even for extended periods of time or for > significant fractions of the keyspace. The underlying routing keys are generated with SHA1. The client keys may be similar, in fact differing in only one character, but that will make a totally different routing key.
> This isn't necessarily bad, but it was a little surprising to me when > I realized it, and it is a way in which NGrouting is not scale-free. That > is: suppose there is a small Freenet where one node receives requests which > are evenly distributed across 0.4 of the keyspace. Suppose there is a > large Freenet where one node receives requests which are evenly distributed > across 0.004 of the keyspace. The former will move 5 of the points after a > few dozen new samples have come in. The latter will move only 2. Needless to say, it's not perfect; requests will be focused around a part of the keyspace, but spread out all over. It's more of a bell curve than a spike. -- http://earth.prohosting.com/tqbay "I love deadlines. I love the whooshing sound they make as they go by." - Douglas Adams Nick Tarleton - [EMAIL PROTECTED] - PGP key available _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
