MapServer vs. Deegree

[Craig Miller]

Thanks Paul.  That's helpful.

Is the FastCGI pooling done per process, or cross-process?
Are there other items that could benefit from cross-process cacheing?  As a
MapServer user, I'm curious as to how MapServer (CGI) compares to Degree
(J2EE) too.

Thanks,
Craig


-----Original Message-----
From: Paul Ramsey [mailto:pramsey at refractions.net] 
Sent: Friday, August 12, 2005 12:06 PM
To: Craig Miller
Cc: MAPSERVER-USERS at LISTS.UMN.EDU
Subject: Re: [UMN_MAPSERVER-USERS] MapServer vs. Deegree

Craig Miller wrote:

> CGI has also been shown to not scale well for a couple of reasons.  It
> creates a new process for each request, and it doesn't re-use memory
> allocations.  In the case of MapServer these concerns are largely moot
> because they aren't significant relative to the time and resources it
takes
> to load data and render a map.  Pooling of PostGIS connections, etc would
be
> a performance improvement however.

FYI: You can pool PostGIS (and more importantly Oracle and SDE) 
connections by moving to FastCGI with Mapserver.  For PostGIS, the 
connection overhead is about 0.15s, and connections are pooled within 
the process, so each CGI invocation only creates one connection.  For 
Oracle and SDE the connection overhead can get up towards 1s depeending 
on authentication regimes, so connection pooling is basically a 
requirement for anything except demonstration/test services.

Paul