[Geoserver-users] GeoServer upgrade issue from 2.2.5

I have a WMS layer using a Rendering Transformation for a parameterized SQL View layer (which calls a database function).
Upgrading from an old version of GeoServer we’ve experienced a massive performance problem with this layer.

When setting logging to verbose, the old version produced SQL something like:

···
SELECT encode(ST_AsBinary(ST_Force_2D("location")),'base64') as "location","myval" FROM (select location, thevalue as myval
from myschema.get_data( 70,50 )) as "vtable" WHERE  "location" && ST_GeomFromText('POLYGON ((-26.823634473210518 6.409727748826477, -26.823634473210518 33.560993640777525, 0.3276314187394202 33.560993640777525, 0.3276314187394202 6.409727748826477, -26.823634473210518 6.409727748826477))', 4326)

The new version shows:

SELECT encode(ST_AsEWKB(“location”),‘base64’) as “location”,“myval” FROM (select location, thevalue as myval from myschema.get_data( 70,50 )) as “vtable”

The lack of spatial filter causes a huge performance problem since about 100 times as many rows are returned and the Barnes Surface transformation gobbles up all the CPU and GeoServer becomes unresponsive.

Any thoughts about what could be causing the spatial filter to no longer be added?

What I’ve read in other threads hasn’t really made this clear to me.

Thanks,

Simon Hartley

.

Should I file this in JIRA as a regression?

Simon

···

From: Simon Hartley [mailto:SHartley@anonymised.com]
Sent: 12 July 2016 17:36
To: geoserver-users@lists.sourceforge.net
Subject: [EXTERNAL][Geoserver-users] GeoServer upgrade issue from 2.2.5

I have a WMS layer using a Rendering Transformation for a parameterized SQL View layer (which calls a database function).
Upgrading from an old version of GeoServer we’ve experienced a massive performance problem with this layer.

When setting logging to verbose, the old version produced SQL something like:

SELECT encode(ST_AsBinary(ST_Force_2D("location")),'base64') as "location","myval" FROM (select location, thevalue as myval
from myschema.get_data( 70,50 )) as "vtable" WHERE  "location" && ST_GeomFromText('POLYGON ((-26.823634473210518 6.409727748826477, -26.823634473210518 33.560993640777525, 0.3276314187394202 33.560993640777525, 0.3276314187394202 6.409727748826477, -26.823634473210518 6.409727748826477))', 4326)

The new version shows:

SELECT encode(ST_AsEWKB(“location”),‘base64’) as “location”,“myval” FROM (select location, thevalue as myval from myschema.get_data( 70,50 )) as “vtable”

The lack of spatial filter causes a huge performance problem since about 100 times as many rows are returned and the Barnes Surface transformation gobbles up all the CPU and GeoServer becomes unresponsive.

Any thoughts about what could be causing the spatial filter to no longer be added?

What I’ve read in other threads hasn’t really made this clear to me.

Thanks,

Simon Hartley

.

*** This communication has been sent from World Fuel Services
Corporation or its subsidiaries or its affiliates for the intended recipient
only and may contain proprietary, confidential or privileged information.
If you are not the intended recipient, any review, disclosure, copying,
use, or distribution of the information included in this communication
and any attachments is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to this
communication and delete the communication, including any
attachments, from your computer. Electronic communications sent to or
from World Fuel Services Corporation or its subsidiaries or its affiliates
may be monitored for quality assurance and compliance purposes.***

Hi Simon,
   I have no experience with rendering transformations, but I would
suggest you first check the basics again (configuration was ported
correctly, test conditions for your two examples are the same).
   Then maybe try finding the change in the WPS module from 2.2.5 to
your current version that triggered that specific behaviour change.
Doing that is a bit over my head right now, but it would provide you
with the exact description of what happened and maybe help you with a
workaround/patch/bug report/performance regression report.

   At first glance I thought it had something to do with the CQL filter,
I did a bit of researching and it doesn't seem to be the case.

Good luck.
--Daniel

Em 15/07/2016 10:13, Simon Hartley escreveu:

Should I file this in JIRA as a regression?

Simon

*From:*Simon Hartley [mailto:SHartley@anonymised.com]
*Sent:* 12 July 2016 17:36
*To:* geoserver-users@lists.sourceforge.net
*Subject:* [EXTERNAL][Geoserver-users] GeoServer upgrade issue from 2.2.5

I have a WMS layer using a Rendering Transformation for a
parameterized SQL View layer (which calls a database function).
Upgrading from an old version of GeoServer we’ve experienced a massive
performance problem with this layer.

When setting logging to verbose, the old version produced SQL
something like:

SELECT encode(ST_AsBinary(ST_Force_2D("location")),'base64') as
"location","myval" FROM (select location, thevalue as myval from
myschema.get_data( 70,50 )) as "vtable" WHERE "location" &&
ST_GeomFromText('POLYGON ((-26.823634473210518 6.409727748826477,
-26.823634473210518 33.560993640777525, 0.3276314187394202
33.560993640777525, 0.3276314187394202 6.409727748826477,
-26.823634473210518 6.409727748826477))', 4326)

The new version shows:

SELECT encode(ST_AsEWKB("location"),'base64') as "location","myval"
FROM (select location, thevalue as myval from myschema.get_data( 70,50
)) as "vtable"

The lack of spatial filter causes a huge performance problem since
about 100 times as many rows are returned and the Barnes Surface
transformation gobbles up all the CPU and GeoServer becomes unresponsive.

Any thoughts about what could be causing the spatial filter to no
longer be added?

What I’ve read in other threads hasn’t really made this clear to me.

Thanks,

Simon Hartley

.

*** This communication has been sent from World Fuel Services
Corporation or its subsidiaries or its affiliates for the intended
recipient
only and may contain proprietary, confidential or privileged information.
If you are not the intended recipient, any review, disclosure, copying,
use, or distribution of the information included in this communication
and any attachments is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to this
communication and delete the communication, including any
attachments, from your computer. Electronic communications sent to or
from World Fuel Services Corporation or its subsidiaries or its
affiliates
may be monitored for quality assurance and compliance purposes.***

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Good idea… with full details to reproduce on a developer machine, like the table demotion, sample data, style and request.

Cheers
Andrea

Il 15 lug 2016 15:56, “Simon Hartley” <SHartley@anonymised.com> ha scritto:

Should I file this in JIRA as a regression?

Simon

From: Simon Hartley [mailto:SHartley@anonymised.com]
Sent: 12 July 2016 17:36
To: geoserver-users@lists.sourceforge.net
Subject: [EXTERNAL][Geoserver-users] GeoServer upgrade issue from 2.2.5

I have a WMS layer using a Rendering Transformation for a parameterized SQL View layer (which calls a database function).
Upgrading from an old version of GeoServer we’ve experienced a massive performance problem with this layer.

When setting logging to verbose, the old version produced SQL something like:

SELECT encode(ST_AsBinary(ST_Force_2D("location")),'base64') as "location","myval" FROM (select location, thevalue as myval
from myschema.get_data( 70,50 )) as "vtable" WHERE  "location" && ST_GeomFromText('POLYGON ((-26.823634473210518 6.409727748826477, -26.823634473210518 33.560993640777525, 0.3276314187394202 33.560993640777525, 0.3276314187394202 6.409727748826477, -26.823634473210518 6.409727748826477))', 4326)
 

The new version shows:

SELECT encode(ST_AsEWKB(“location”),‘base64’) as “location”,“myval” FROM (select location, thevalue as myval from myschema.get_data( 70,50 )) as “vtable”

The lack of spatial filter causes a huge performance problem since about 100 times as many rows are returned and the Barnes Surface transformation gobbles up all the CPU and GeoServer becomes unresponsive.

Any thoughts about what could be causing the spatial filter to no longer be added?

What I’ve read in other threads hasn’t really made this clear to me.

Thanks,

Simon Hartley

.

*** This communication has been sent from World Fuel Services
Corporation or its subsidiaries or its affiliates for the intended recipient
only and may contain proprietary, confidential or privileged information.
If you are not the intended recipient, any review, disclosure, copying,
use, or distribution of the information included in this communication
and any attachments is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to this
communication and delete the communication, including any
attachments, from your computer. Electronic communications sent to or
from World Fuel Services Corporation or its subsidiaries or its affiliates
may be monitored for quality assurance and compliance purposes.***


What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev


Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Thank you very much.

I have created the following ticket:
https://osgeo-org.atlassian.net/browse/GEOS-7641

Simon

···

Il 15 lug 2016 15:56, “Simon Hartley” <SHartley@…2992…> ha scritto:

Should I file this in JIRA as a regression?

Simon

From: Simon Hartley [mailto:SHartley@…2992…]
Sent: 12 July 2016 17:36
To: geoserver-users@lists.sourceforge.net
Subject: [EXTERNAL][Geoserver-users] GeoServer upgrade issue from 2.2.5

I have a WMS layer using a Rendering Transformation for a parameterized SQL View layer (which calls a database function).
Upgrading from an old version of GeoServer we’ve experienced a massive performance problem with this layer.

When setting logging to verbose, the old version produced SQL something like:

SELECT encode(ST_AsBinary(ST_Force_2D("location")),'base64') as "location","myval" FROM (select location, thevalue as myval
from myschema.get_data( 70,50 )) as "vtable" WHERE  "location" && ST_GeomFromText('POLYGON ((-26.823634473210518 6.409727748826477, -26.823634473210518 33.560993640777525, 0.3276314187394202 33.560993640777525, 0.3276314187394202 6.409727748826477, -26.823634473210518 6.409727748826477))', 4326)
 

The new version shows:

SELECT encode(ST_AsEWKB(“location”),‘base64’) as “location”,“myval” FROM (select location, thevalue as myval from myschema.get_data( 70,50 )) as “vtable”

The lack of spatial filter causes a huge performance problem since about 100 times as many rows are returned and the Barnes Surface transformation gobbles up all the CPU and GeoServer becomes unresponsive.

Any thoughts about what could be causing the spatial filter to no longer be added?

What I’ve read in other threads hasn’t really made this clear to me.

Thanks,

Simon Hartley

.

*** This communication has been sent from World Fuel Services
Corporation or its subsidiaries or its affiliates for the intended recipient
only and may contain proprietary, confidential or privileged information.
If you are not the intended recipient, any review, disclosure, copying,
use, or distribution of the information included in this communication
and any attachments is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to this
communication and delete the communication, including any
attachments, from your computer. Electronic communications sent to or
from World Fuel Services Corporation or its subsidiaries or its affiliates
may be monitored for quality assurance and compliance purposes.***


What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users