Changes between Version 59 and Version 60 of Check

Timestamp:

Oct 29, 2010, 4:58:46 PM (14 years ago)

Author:

alexandru.olteanu

Comment:

--

Check

@@ -359 +359 @@
 == Demo ==
 
-For demo purposes, we have build two islands, using Raven and Sparrow nodes, each of the islands being connected through a SAM7X edge router to the gateway running on PC. For our demo scenario, let's suppose the two islands are adjacent (e.g. in the same building), although they really were hundreds of kilometers away, one in Bucharest and one in Dresden. Also let's imagine that we need to measure the mean temperature of the area covered by the islands.
+For demo purposes, we have build two islands, using Raven and Sparrow nodes, each of the islands being connected through a SAM7X edge router to the gateway running on PC. For our demo scenario, let's suppose the two islands are adjacent (e.g. in the same building). Also let's imagine that we need to measure the mean temperature of the area covered by the islands.
 
 To simulate node failure, the nodes can be simply unplugged from their power source or the service running on them can be suspended using the appropriate URL, such as [http://localhost:8000/babe-00ff-fe00-0001/service/temp/stop]
@@ -399 +399 @@
 Acting beyond the gateway level, the Self-healing service is able to compensate the lack of sensors in one island, with sensors in another island.
 
-For this demo, we are using two islands, each with two nodes capable of measuring temperature. At the start, the temperature service on the two nodes in island1 (the Dresden island) is switched off and the temperature service on island2's nodes (the Bucharest island) is switched on.
+For this demo, we are using two islands, each with two nodes capable of measuring temperature. At the start, the temperature service on the two nodes in island1 is switched off and the temperature service on island2's nodes is switched on.
 
 Running the test client shows that, without the help of the Self-healing sensor, the sensor readings lack inputs as nodes start failing.
@@ -413 +413 @@
 === Performance ===
 
-The lag between the detection of a node failing and restoring the service, by turning it on for another node, is some tens of miliseconds. We have tried a few measurements, for both local islands and remote islands. In these examples, the Self-healing service is running in the same network as the Bucharest island and we introduce node failures causing node starts in both Bucharest and Dresden islands.
+The lag between the detection of a node failing and restoring the service, by turning it on for another node, is some tens of miliseconds. We have tried a few measurements, for both local islands and remote islands. In these examples, the Self-healing service is running in the same network as island2 and we introduce node failures causing node starts in both islands.
 
 [[Image(sh-performance.png, center, 600px)]]
@@ -419 +419 @@
 The data from the above screenshot is better shown in this table:
 
-||= Test no. =||= Node started =||= Detection time [s] =||= Service restored time [s] =||= Lag [ms] =||
+||= Test no. =||= Node started =||= Timestamp of detection [s] =||= Timestamp for service restoration [s] =||= Lag [ms] =||
 || 1 || remote || 24.182 || 24.297 || 115 ||
 || 2 || local || 30.741 || 30.775 || 34 ||