We have the following GeoServer setup: Datastore to an Oracle 12c Exadata instance Internal connection pooling No schema specified
We noticed a serious performance anomaly, where each layer was taking about 4 s to render, even when the data was very small. When we switched to specifying an explicit schema in the Datastore config, the performance got significantly faster, and the time to render individual layers became more proportional to the query result size. So the questions are: 1. does omitting a schema name in the Oracle Datastore config cause connection pooling to be disabled or defeated? 2. Will this issue be avoided when using a JNDI connection pool? If the answer to # 1 is yes, this should probably be highlighted in the docs...
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
