s.notice_radius is also 750.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Mapserver-User-f4226646.html
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users
Ahlah,
Mapserver does the following that should take some additional
time:encode(ST_AsBinary(ST_Force_2D("point"),'NDR'),'hex') as geomYou can
execute the whole query in PostgreSQL and notice the increase of time.
One question: s.notice_radius FROM (SELECT * FROM roronline.settings LIMIT 1)
AS
As I told I copied both Postgis queries from logs to pgAdmin and ran them
without MapServer. Both took about 200ms. So it seems that bottleneck is in
Mapserver.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Mapserver-User-f4226646.html
___
Hi ahti,
are you sure it si not postgis? Using the fixed radius it takes 10
seconds, with the radius from the other table it takes < 1 second until
mapserver gets the result, have a look at line 16 and 17 of your logs:
> [Tue Sep 4 14:39:39 2018].545070 msPostGISLayerWhichShapes query: ...
>
I try to show a polygon on map by creating a buffer around point in Postgis
(by ST_Buffer) but Mapserver has a strange performance problem.
If I put hardcoded radius to ST_Buffer query, rendering takes about 10
seconds although query result is empty. If I set the same value to radius by
reading it
