Tim,
FastCGI does not require thread-safety. You will find your SDE tests
work much much better with fcgi: in fact, the fcgi support got
finished precisely because of an SDE contract we were working on that
needed to get decent performance. Don't forget to defer connection
closing in your map file, otherwise you'll get no benefit from the
fcgi connection pool. We found that 2-3 mapserver fcgi processes per
CPU was the sweet spot. The fcgi module queues up requests if all
the child processes are busy, which is actually preferable to running
them all concurrently (and making them all finish slower). It is a
nice way to smooth out bursts of load so they don't simply drop the
machine to it's knees by firing up 10 concurrent mapservers.
Paul
On Mar 2, 2006, at 9:36 PM, tim wrote:
anks Frank. Does 'normal' cgi use include --with-fastcgi? the
mapserver I am building gets almost all its data from a variety of sde
servers (think large state govt depts). In our testing so far (4.6.2
and 4.8.1) we keep hitting the limit of sde's connections before we
hit
mapservers limits (though we do have good hardware: Dell 3ghz dual
xeons
with 4gb ram), hence our decision to re-do testing with fastcgi.
Thanks,
Tim
--
Mapforge Geospatial
Level 3/ 267 St Georges Tce
Perth 6000
Western Australia
