[Gzz-commits] gzz/Documentation/misc/hemppah-progradu researc...

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Hermanni Hyytiälä <address@hidden>      03/01/23 03:26:59

Modified files:
        Documentation/misc/hemppah-progradu: research_problems 

Log message:
        Some thoughts on Tuomas' 'jyu-scenario'

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/research_problems.diff?tr1=1.27&tr2=1.28&r1=text&r2=text

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/research_problems
diff -u gzz/Documentation/misc/hemppah-progradu/research_problems:1.27 
gzz/Documentation/misc/hemppah-progradu/research_problems:1.28
--- gzz/Documentation/misc/hemppah-progradu/research_problems:1.27      Tue Jan 
21 07:43:36 2003
+++ gzz/Documentation/misc/hemppah-progradu/research_problems   Thu Jan 23 
03:26:59 2003
@@ -152,6 +152,7 @@
 Hybrid:                N/A             N/A             N/A
 Social:                N/A***          N/A***          N/A***
 Skip graphs 1): O(log n)       O(log n)        O(log n)
+Symphony:      O(log^2 n)      O(log n)        O(log n)
 
 * = In Kademlia, there is no action required when nodes leaves the system
 
@@ -791,6 +792,13 @@
 
 Tuomas' example scenario #2:
 'What will happen if, jyu's network connection is broken ? Inside jyu network, 
how do we/system will self-organise ?'
+
+It seems to be that DHTs are unable to self-reorganise after a sudden 
partitioning, because
+a) every node has a fixed space in identifier space
+b) system has a fixed identifier space, e.g. Pastry and Chord require a priori 
knowledge about the size of the system
+c) even if system is able self-reorganise, the key space is not uniformly 
distributed anymore -> all nodes have to leave/rejoin --> lot of traffic
+
+The question is: how well SWAN can self-organise ?
 
 Half-life phenomenon \cite{libennowell01observations}
 Current decentralized, but structured \cite{chord, can, pastry, Tapestry etc.) 
ignores the fact