performance with different data formats

[Frank Warmerdam]

Mark Adams wrote:
> Harold, 
> 
>> Ensure that 'mapserv -v' shows SUPPORTS=FASTCGI.
> 
> Yes, that's clear.

Mark,

Note, this presumably doesn't matter when you are using PHP Mapscript.
This mostly just affects the mapserv.exe mainline.

>> Set your FastCgiConfig in your apache configuration to be something
>> similar to step 3 of the FastCGI howto.  
> 
> Well, we're not using Apache - all of our clients use IIS, so that's the
> environment we work in as well. So we're on Windows 2003 server with
> IIS. The comments in the fastcgi howto document regarding implementing
> this on Win32 are pretty scary, and all are about Apache, not IIS. In
> our case we used the fastcgi ISAPI dll, and have linked PHP to that dll
> in a php web server extension. But we had no idea what if anything we'd
> have to do to link mapserver to that dll. (Are we really the only folks
> in the mapserver world that run on IIS?!)

Perhaps the only PHP MapScript IIS FastCgi user who feels like talking
about it on the mailing list?

>> And the most important bit
>> is ensure that 'PROCESSING="CLOSE_CONNECTION=DEFER" is set on the
>> MAP, or else MapServer will not do *any* connection pooling
>> (FastCGI or not).
> 
> We have tried both to include and not include the PROCESSING directive.
> It didn't make a noticeable difference to include. Does this again imply
> that we haven't got fastcgi configured properly?

If you have layer debugging turned on for the layer, and capture the output
somewhere, you should see debug messages about when connections are being
created and destroyed.

For instance, msConnPoolClose() messages will be issued when a connection
is actually closed.

If you can see these messages in the log, you should get a much better
idea of whether connection pooling is doing anything for you or not.

I appologise for not having followed the whole discussion closely.  As
has been suggested I think, connection pooling won't solve problems with
MapServer's "record by record" fetching when using query mode.  Issuing an
SQL query for each record needed can be quite a killer.

Rendering just uses one SQL query for the whole resultset, by comparison.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org