[Gzz-commits] fenfire/docs/pegboard/storm_gisp_simulation--he...

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/fenfire
Module name:    fenfire
Changes by:     Hermanni Hyytiälä <address@hidden>      03/06/02 09:30:40

Modified files:
        docs/pegboard/storm_gisp_simulation--hemppah: peg.rst 

Log message:
        try to remove

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/storm_gisp_simulation--hemppah/peg.rst.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: fenfire/docs/pegboard/storm_gisp_simulation--hemppah/peg.rst
diff -u fenfire/docs/pegboard/storm_gisp_simulation--hemppah/peg.rst:1.1 
fenfire/docs/pegboard/storm_gisp_simulation--hemppah/peg.rst:1.2
--- fenfire/docs/pegboard/storm_gisp_simulation--hemppah/peg.rst:1.1    Mon Jun 
 2 07:01:56 2003
+++ fenfire/docs/pegboard/storm_gisp_simulation--hemppah/peg.rst        Mon Jun 
 2 09:30:40 2003
@@ -1,12 +1,12 @@
 
-==========================================================================
-PEG storm_gisp_simulation--hemppah:
-==========================================================================
+=================================================================================
+PEG storm_gisp_simulation--hemppah: Storm P2P simulations using the GISP 
protocol
+=================================================================================
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-06-02
-:Last-Modified: $Date: 2003/06/02 11:01:56 $
-:Revision: $Revision: 1.1 $
+:Last-Modified: $Date: 2003/06/02 13:30:40 $
+:Revision: $Revision: 1.2 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -39,18 +39,18 @@
 Research problems
 =================
 
-By using simulation as a research method, we try to test different kind of
-properties of the GISP protocol. There are three research problems which
-we try to solve using simulation:
+By using simulation as a research method, we try to test different kinds of
+properties of the GISP protocol. There are number of research problems which
+we try to solve using the simulation process:
 
-1) How well GISP can scale is there are lot of concurrent peer joins and
+ - How well GISP can scale is there are lot of concurrent peer joins and
    leaves in the system ? What about effieciency ?
          
-2) How well GISP gisp is able to perform in adverse conditions, e.g., a
+ - How well GISP gisp is able to perform in adverse conditions, e.g., a
    network partition occurs ?
    
-3) How well GISP gisp is able to perform against different kind of
-   security attacks ?
+ - How well GISP gisp is able to perform against different kind of
+   security attacks and what are the impacts ?
 
 
 Hypothesis
@@ -65,15 +65,33 @@
  - GISP cannot scale well when peers join and leave the system at a 
    (huge) variable rate for a given time period
    
- - GISP peer is not able to handle all request properly when great amount 
+ - A GISP peer is not able to handle all request properly when great amount 
    of query requests are performed toward a single peer (a peer is 
-   responsible for a given key)
+   responsible for a given key). Thus, there can be query hotspots
+   in the system.
    
  - GISP can scale well if the number of peers and and Storm blocks
-   increase side by side
-     
- - GISP is not able to self-organize efficienly after a fatal network
+   increase side by side and logarithmic efficiency still holds
+
+ - GISP can well if there are heterogeneous peers and logarithmic 
+   data lookup efficiency still holds
+ 
+ - A java based GISP implementation does not consume much memory if
+   it requires less than X Mb of memory
+ 
+ 
+Adverse conditions
+------------------
+
+ - GISP is not able to self-organize fast enough/efficienly after a fatal 
network
    partition, i.e., half of the peers "die" suddenly 
+ 
+ 
+Security
+--------
+ 
+ - A hostile entity is able to reroute a data lookup to a incorrect 
+   destination peer during a data lookup process
 
 
 Issues