[mapguide-internals] Raster provider problems...

[Robert Bray]

Hmm,

Introducing this is a good thing. The resolution is to single thread the 
GDAL provider (and any other provider that supports less than per 
connection threaded) to prevent the server from crashing under load. We 
really have no choice. To be honest, I am surprised that users using the 
GDAL provider have not complained of problems or maybe this is the 
source of some of the stability issues and we just have not caught it 
because we did not protect the server from non thread safe providers.

FYI - MapGuide 6.x has single threaded Raster data and DWG data since 
those formats were first supported. Yes it is a limitation, but one 
users have been living with for years.

Bob

Jason Birch wrote:
> Hi all,
>  
> I'm concerned about the lack of discussion of the change which resulted in this:
> http://trac.osgeo.org/mapguide/ticket/39 <http://trac.osgeo.org/mapguide/ticket/39> 
>  
> If GDAL is not thread safe, nor easily made thread-safe (which I imagine could easily be the case since it relies on external libraries) then we're going to have a lot of upset users.  I know that it pretty much dead-ends me at 1.1 until it is resolved.  
>  
> I am also worried that this oversight happened, considering that at least some folks were aware of the single-threaded nature of the GDAL provider. Multithreading was mentioned as a benefit of the ADSK raster provider at AU.
>  
> If MapGuide requires a certain level of implementation from FDO providers but does not test against the full suite of providers or at least publish and maintain this minimum compliance level, we are going to find ourselves in this situation again.
>  
> Jason
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>