Fast-cgi is one process that manages all your connections (acts more like apache module) cgi creates a new process for every connection so fast-cgi is faster and consumes less resources. The best performance you should get with tilecache serving TMS(If it's supported by your client, openlayers supports it), images are request directly so there is almost no overhead
On Wed, Oct 21, 2009 at 10:42 AM, Adrian Popa <[email protected]> wrote: > Hello, sorry for this noobie question, but I have been running mapserver as > a cgi process and sometimes I need to make lots of calls to it to get the > data I want. I have used TileCache to get the layers I need and which don't > change over time and it speeds things up considerably. > > I was wondering - is it possible (and is it more efficient?) to run > mapserver as fast-cgi? Would it increase speed? The mapserver in the cgi-bin > directory is already a binary file - so I'm not sure if fast-cgi would do > any good. > > Also, would I have any extra speed benefits if I make WMS queries instead of > regular cgi queries? > > Thank you, > Adrian > > _______________________________________________ > mapserver-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapserver-users > -- http://iap.md, The future is open _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
