Apache should be plenty quick. Start with using fastcgi and optimizing your data: e.g. create spatial indexes, use optimized raster formats and then optimizing your configuration (scale dependent layers w/things like reduced resolution layers where possible). -Steve
From: mapserver-users-boun...@lists.osgeo.org [mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of Peter Maes Sent: Friday, December 09, 2011 6:31 AM To: mapserver-users@lists.osgeo.org Subject: [mapserver-users] Mapserver performance on apache - heavy load systems Hi all, We are planning to launch a major mapserver production site where i'm required to launch many mapserver instances in some form of cluster. So I basically have some questions related to this: - Does anyone have good tips on performance for running mapserver on apache? - Any specific build parameters I should pay attention to? - Does it run as a native apache module, or is it required to work through cgi? In which case: will i get better performance by using fastcgi? (we are not using databases but shapefiles). - Should I consider lighttpd or nginx instead? - Any other tips related to clustering mapserver instances? :). Note that we are using live data, so we cannot cache them, except for a minute or so. Thanks for your time.
_______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
