[mapserver-users] SDE performance

[C F]

Regarding MapServer creating a NEW db connection for each db layer.... is 
anyone else taking this seriously?  I thought this would be just the 
beginning of the discussion but there doesn't seem to be too much interest 
in this besides us few.  This seems like a pretty unnecessary performance 
constraint.  I would think that it would be a fairly easy fix, but it's not 
my place to be making those assumptions... But I just thought I'd bring it 
up again in case everyone forgot :)


>From: Jan Hartmann <jhart at frw.uva.nl>
>To: mapserver-users at lists.gis.umn.edu
>Subject: Re: [mapserver-users] SDE performance
>Date: Wed, 13 Nov 2002 11:57:40 +0100
>
>My impression is that this would not be very hard to implement: just a 
>global array with pointers to every CONNECTION opened in all LAYERS. The 
>applications itself (PostGIS, SDE, Oracle) could test for already open 
>connections. The only thing MapServer itself would have to do is closing 
>all connections at the end.
>This would certainly be of great help for Oracle and SDE users; large 
>connection overheads have been mentioned regularly on this list. Even for 
>PostGIS there are advantages; think about reusing complex queries with 
>spatial operators and TMP tables. IMHO certainly worth looking into!
>
>Jan Hartmann
>
>
>Paul Ramsey wrote:
>>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.
>>
>
>Jan Hartmann
>Department of Geography
>University of Amsterdam


_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail