Andy's correct, the mapfile parse overhead is so small as to be almost unmeasurable (I once tried). FCGI re-parses every time. It's a good thing, makes working w/ FCGI transparent.
P. On Fri, Jan 3, 2014 at 2:41 PM, Andy Colson <[email protected]> wrote: > On 1/3/2014 4:08 PM, Richard Greenwood wrote: >> >> I'm running FastCGI but I'm not sure that I have it configured >> optimally, or even correctly. I have about a dozen map files. My >> requests look like: >> mapserv.fcgi?map=abc.map&... >> mapserv.fcgi?map=def.map&... >> mapserv.fcgi?map=ghi.map&... >> Does FCGI know to cache each map file so that I have a FCGI thread(s) >> for each map file? Or do I just have FCGI threads that are re-reading >> which ever map file is needed? Would I do better with a small script >> wrapper around each mapserv+mapfile like: >> abc.fcgi >> def.fcgi >> ghi.fcgi >> Sorry - I don't feel like I'm articulating my question very well. >> >> Rich >> >> -- >> Richard Greenwood >> [email protected] <mailto:[email protected]> >> www.greenwoodmap.com <http://www.greenwoodmap.com> >> >> >> _______________________________________________ >> mapserver-users mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/mapserver-users >> > > I believe it'll reload the .map file every request. But, your OS should > cache it so you wont actually be hitting disk, and reading/parsing a .map > file is very quick. I think this is pretty far down on the list of things > to optimize. (Well, thats my opinion. I've never actually timed it) > > -Andy > > _______________________________________________ > mapserver-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapserver-users _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
