Changes between Version 7 and Version 8 of MapGuideRfc90

Timestamp:

Nov 4, 2010, 1:13:29 AM (14 years ago)

Author:

uvlite

Comment:

--

MapGuideRfc90

@@ -20 +20 @@
 == Overview ==
 
-Add support internally to the MapGuide Server Engine to render larger tiles
-and then slice them up into the normal tile sizes
+Add support internally to the MapGuide Server Engine to map tile requests to larger meta tiles
+and then slice them up into the standard tile sizes. 
 
 == Motivation ==
 
-With complex maps, it's more efficent to render one large tile than many small ones. 
+With complex maps, it's more efficient to render one large tile than many small ones. 
 There is little or no benefit for simple maps like the Sheboygan Sample.[[BR]]
 
-Using our 140 layer example map we can observer the following timing using metatilefactor 1 & 4
+Using our 140 layer example map we can observe the following timing using metatilefactor 1 & 4
 and 3 different locking strategies in the attached chart MetatilingChart1.jpg.
 
 == Proposed Solution ==
 
-Add a meta tile factor to the tile service, which then will render larger tiles
-and then slice them up into the smaller tiles which get served to clients.
+Add a meta tile factor to the tile service, which then will render larger tiles enlarged by the provided factor.
+to be sliced up into the smaller tiles which then get served to clients.
+e.g.[[BR]]
+Client -> GetTile(0,1) -> RenderMetaTile(0,0 - 1,1) -> SplitUp -> ReturnTile (0,1)
+       -> GetTile(1,1) -> wait................................... ReturnTile (1,1)
 
 == Issues ==
 
 Locking the threads to the implicit producer consumer scheme is complex and
-file locking seems not very efficient. To improve polling delay the Polling
+the file locking seems not very efficient. To improve polling delay the Polling
 configuration value has been changed to ms semantics so we can specify 500ms.
 
-In addition a ace_condition has been implemented to get rid of the lockfiles 
+In addition an ace_condition has been implemented to get rid of the lockfiles 
 all together and further improve the response time. (LockMethod == 3)
 In addition to the standard approach with one lock per sub tile (LockMethod == 2)
@@ -49 +52 @@
 == Implications ==
 
-When using a meta tiling factor of 4, 15 tiles will wait while the meta tile is rendered
+For example when using a meta tiling factor of 4, 15 tiles will wait while the meta tile is rendered
 and sliced up. A most efficient locking scheme will have significant effect on this behaviour.
 
@@ -55 +58 @@
 == Test Plan ==
 
-The output of a tile map request should be indentical whether served 
-with meta tiling enabled or without. 
+The output of a tile map request should be identical whether served with meta tiling enabled or without. 
 
 == Funding/Resources ==