[mapguide-internals] WFS performance problem

[Gabriele Monfardini]

Hi Jackie,

> There's something *really* wrong with the WFS output implementation. It's
> doesn't stream out the response of MgFeatureService::GetWfsFeature, it reads
> that whole stream into memory first before writing out the HTTP response.
>
> See:
> http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/HttpHandler/HttpWfsGetFeature.cpp#L279
>
> Why it does this I do not know.
>
> This is probably a related issue: http://trac.osgeo.org/mapguide/ticket/1070
>
> The test case in question doesn't happen anymore, because the storage limit
> of MgByte (the backing store for memory-based streams) was raised from 16MB
> to 64MB, effectively sweeping this particular issue under the carpet, but
> the problem still remains of huge temporary spikes in mem usage when WFS
> GetFeature is invoked.

thank you for your interesting reply.
Supporting OGC standard is becoming more and more important.
I hope that Mapguide implementation will receive some love in future releases.

Regards,

Gabriele