[mapserver-users] SDE performance

[Paul Ramsey]

Mapserver account for mailing list wrote:
 > Would it not
 > make more sense to permit a nesting of layer objects inside a
 > 'connection object' so that one single connection could be made for
 > multiple layer requests (I am not proposing this, simply exemplifying
 > how the number of connection transactions could be reduced).

For PostGIS and OracleSpatial, this is also an issue. As the number of 
layers which are generated from the database for a given map growns, the 
number of redundant connection calls also grows. For PostgreSQL, it is 
not a *huge* issue, because connection overhead is relatively low. For 
OracleSpatial it *is* quite a large issue, because Oracle connection 
time overhead is relatively large. The same thing might hold for SDE. 
Bottom line, it is silly to be creating and tearing down these 
connections over and over when the data is being read from the same place.

One possibility would be to abstract the connection making process a 
bit, so that a 'getConnection' function first checks a hash to see if 
there is already a connection with parameters which match the requested 
connection. It would probably have to reside on the mapObj though...

P.

-- 
       __
      /
      | Paul Ramsey
      | Refractions Research
      | Email: pramsey at refractions.net
      | Phone: (250) 885-0632
      \_