Quick reminder for the archives: the reason for the USE_POINT_Z_M option is that there is (or at least used to be at the time) a non trivial performance impact (15%-50% performance hit) likely related to the increase in size of the pointObj struct when Z and M are added:

https://github.com/mapserver/mapserver-import/issues/1244

It may be nice to have some updated benchmarks comparing with and without USE_POINT_Z_M with recent releases, but I just wanted to point out that if one cares about performance and doesn't need the Z,M then is preferable to keep this option turned off in their builds.

Daniel


On 2017-06-30 9:31 AM, Jeff McKenna wrote:
On 2017-06-30 8:00 AM, Michael Smith wrote:
What os? I know the mapserver docker packages (https://hub.docker.com/r/mapserver/mapserver/) have it but most of the windows versions, MS4W, GisInternals, don’t. Don’t know about OSGeo4W.



Thanks for mentioning this Mike, I've filed a ticket to include this in the upcoming MS4W release: http://www.ms4w.com/trac/ticket/120


-jeff





--
Daniel Morissette
Mapgears Inc
T: +1 418-696-5056 #201
_______________________________________________
mapserver-users mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Reply via email to