Mapserver/PostGIS Performance Tips31 Oct 2008
I’m working on re-writing the PostGIS driver in Mapserver to clean it up a little and hopefully make it faster, and seeing the flow of control, there are a couple ways users of the existing driver can improve performance with small configuration changes. The simplest syntax for defining a PostGIS layer in Mapserver is just:
DATA "the_geom from the_table"
Very simple, but: how does Mapserver know what primary key to use in queries? And what SRID to use when creating the bounding box selection for drawing maps? The answer is, it asks the database for that information. With two extra queries. Every time it processes the layer.
However, if you are explicit about your unique key and SRID in configuration, Mapserver can, and does, skip querying the back-end for that information.
DATA "the_geom from the_table using unique gid using srid=4326"
Also, if you have more than one PostGIS layer in your map file, you should turn on the Mapserver connection pool, even if you’re not running in FastCGI mode. That’s because the pool will allow all the layers to reuse the same connection. If you have have seven PostGIS layers, at 15ms per connection, that’s 90ms saved (you still pay 15ms for the first connection).
Add this line at the end of each PostGIS layer to tell Mapserver to leave the connection open for future layers:
Go fast, fast, fast!