[mapserver-users] fast cgi MapServer (version 6.0.3) vs cgi with awms getmap request

[Eichner, Andreas - SID-NLKM]

Hello Karsten,

> I just tested fast cgi MapServer (version 6.0.3) vs cgi with 
> a wms getmap
> request againtst a map file with 73 postgis layers (and PROCESSING
> "CLOSE_CONNECTION=DEFER" setting for each layer.)

IMHO that processing option avoids reopening a connection to the same
database for a single request. Once the request is done the
the connection will be closed.

> rendering speed shows that fastcgi is bascially at the same 
> speed or slower than cgi so far

FastCGI only reduces the startup time (as the processes are already
running)
and therefore improves mostly simple requests where startup time is
significant
compared to content generation - like GetCapabilities and
GetLegendGraphic.
In your case parsing the map file with 73 layers already introduces a
significant
workload for every request, independent of the request type.
  That gap should be closed by mod_mapserver which associates a map file
with an URI and keeps a copy of the parsed object in memory wich
usually keeps database connections open.

HTH