<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>MapGuide RFC 13 - Configurable tile size</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2>Hi Jason,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2>I like GetDefaultTileSizeX()/Y(). It gives
an indication that the tile size may be set elsewhere. Currently,
these settings would have to be set identically on the site server and each
support server. I don't believe we have a configuration propagation
mechanism in place. Different tile sizes would lead to a corrupted tile
set.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2>I have not done any internal testing with tiling
support servers. However, a single CPU running full out against a 90 layer
map and a large SDF data set can generate nearly 200MB/sec of disk
traffic. I suspect most of this is spatial index queries. Windows
and Linux do a good job of caching the file system so this ends up being 200MB/s
of memory traffic and not physical disk traffic.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2>Given these data rates, I would expect there to be a
lot of inter-service communication going on as well. The support servers
should probably be configured with FeatureService, MappingService,
RenderingService, and TileService on the same box. The only thing missing
is ResourceService. So it might just be easier to run multiple site
servers similar to the old MapGuide 6.x model.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2>Thanks,<BR>Trevor</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=359114517-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><FONT face=Arial color=#0000ff
size=2></FONT><FONT face=Arial color=#0000ff size=2></FONT><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mapguide-internals-bounces@lists.osgeo.org
[mailto:mapguide-internals-bounces@lists.osgeo.org] <B>On Behalf Of </B>Jason
Birch<BR><B>Sent:</B> Monday, January 29, 2007 10:31 AM<BR><B>To:</B> MapGuide
Internals Mail List<BR><B>Subject:</B> RE: [mapguide-internals] MapGuide RFC 13
- Configurable tile size<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=327120417-29012007><FONT face=Arial
color=#0000ff size=2>This is a good first step. My long-term preference
would be to leave the MapDefinition as accepting the server default tile size,
and implementing a new construct as suggested by Andy to abstract TileGroups so
that they can be reused across MapDefinitions. That gets complicated when
you have more than one TileGroup in a single map though :)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=327120417-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=327120417-29012007><FONT face=Arial
color=#0000ff size=2>At some point, the front end is going to have to make up to
two calls to determine the tile size. I think that it makes sense to have
the calls in the TilingService, but at some point the front ends are
going to have to check the tile size on both a Service and Map/TileGroup
level. Would it make sense to call these
methods GetDefaultTileSize(X|Y) ?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=327120417-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=327120417-29012007><FONT face=Arial
color=#0000ff size=2>Will the tile size setting be on a
per-site-server level? If you have multiple tiling support servers
set up (I'm not even sure if this is possible) will they inherit the
settings from the main server, or need to be configured individually?
What happens if they have different settings?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=327120417-29012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=327120417-29012007><FONT face=Arial
color=#0000ff size=2>Jason</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mapguide-internals-bounces@lists.osgeo.org
[mailto:mapguide-internals-bounces@lists.osgeo.org] <B>On Behalf Of </B>Trevor
Wekel<BR><B>Sent:</B> Monday, January 29, 2007 09:02<BR><B>To:</B> MapGuide
Internals Mail List<BR><B>Subject:</B> [mapguide-internals] MapGuide RFC 13 -
Configurable tile size<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format --><BR>
<P><FONT face=Arial size=2>Hello List,</FONT> </P>
<P><FONT face=Arial size=2>I would like to submit the following RFC for open
discussion and comments:</FONT> <BR><A
href="http://wiki.osgeo.org/index.php/MapGuide_RFC_13_-_Configurable_tile_size"><U><FONT
face=Arial color=#0000ff
size=2>http://wiki.osgeo.org/index.php/MapGuide_RFC_13_-_Configurable_tile_size</FONT></U></A>
</P>
<P><FONT face=Arial size=2>Please respond to the list with any feedback and I
will be happy to respond.</FONT> </P>
<P><FONT face=Arial size=2>Thanks,</FONT> <BR><FONT face=Arial size=2>Trevor
Wekel</FONT> </P></BODY></HTML>