[mapserver-users] Big Maps

[Keith Baker]

Hi,
	I was wondering if people could point me in the direction of optimizing
mapserver for large datasets.  I am looking at doing the entire world in
as much detail as I can find online.  I am trying to decide between
postgres, large shapefiles, and what seems to be a tiling index form the
mapserver docs.
I can 
A) Build Huge shapefiles and let mapserver deal (which it seems to 		do
ok!)
B) Build small tiles and build a postgress DB to feed mapserver
C) Build small tiles and build this 	
TILEINDEX

    Full filename for the index or tile definition for this layer.
Similar to an ArcInfo library index, this shapefile contains polygon
features for each tile. The item that contains the location of the tiled
data is given using the TILEITEM parameter. If the DATA parameter
contains a value then it is added to the end of the location. If DATA is
empty then the location should contain the entire filename.

What speed trade-offs will I see?  Is there a Large-Map Howto
somewhere?  All I could find in the examples were small data sets
compared to what I'm looking at...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20021030/1bc1a41a/attachment.sig>