Re: [Geoserver-users] Catalog initialization slow
Mark I tried creating a GEOMETRY_COLUMNS table as you had suggested. Unfortunately there is no performance gain from doing that. It uses that new table rather than the oracle user_sdo_geom_metadata table, but still does an open connection, query, then close connection for each layer. I was hoping it would query the table once for all the data, then use that for each layer. The gt_pk_metadata table I created is being used but is quicker (even though it does the same for each layer open connection, query, close connection) because it can get all of the view's keys in one query versus a query for each key's column name. Bob -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Catalog initialization slow
Op wo 4 apr. 2018 20:28 schreef Robertafoster8: > Thanks Mark for the reply and suggestion - I will try adding the > GEOMETRY_COLUMNS table as you suggested. > > Any thoughts on having the initialization been kicked off when the > GeoServer > war is deployed? I was thinking of tying a rest call in the init() section > of a servlet filter. > > Bob > If you want to go that route I'd just use curl from a batch file doing a describefeaturetype request > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Catalog initialization slow
Thanks Mark for the reply and suggestion - I will try adding the GEOMETRY_COLUMNS table as you suggested. Any thoughts on having the initialization been kicked off when the GeoServer war is deployed? I was thinking of tying a rest call in the init() section of a servlet filter. Bob -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Catalog initialization slow
2018-03-29 1:44 GMT+02:00 Robertafoster8: > I have a GeoServer 2.9.4 configuration with about 150 layers that use an > Oracle spatial database. They use a oracle JNDI data store. I have > GeoServer deployed in a weblogic cluster using the same data directory and > no tile cache. Each layer used a view in oracle. > > When the war is deployed the wms layers are available very quickly to > server > png images to the client. As soon as a wfs getfeature is sent to GeoServer > it kicks off the feature catalog init which takes about 10 minutes. > > I was able to speed up the catalog init by creating a gt_pk_metadata table. > > Are there other ways to speed this up? > If you don't have one already you may want to add a GEOMETRY_COLUMNS table see: http://docs.geoserver.org/latest/en/user/data/database/oracle.html Also upgrading to a current release will get you all the speed enhancements that were made over the last year-and-a-half Mark -- Disclaimer; This message is just a reflection of what I thought at the time of sending. The message may contain information that is not intended for you or that you don't understand. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] Catalog initialization slow
I have a GeoServer 2.9.4 configuration with about 150 layers that use an Oracle spatial database. They use a oracle JNDI data store. I have GeoServer deployed in a weblogic cluster using the same data directory and no tile cache. Each layer used a view in oracle. When the war is deployed the wms layers are available very quickly to server png images to the client. As soon as a wfs getfeature is sent to GeoServer it kicks off the feature catalog init which takes about 10 minutes. I was able to speed up the catalog init by creating a gt_pk_metadata table. Are there other ways to speed this up? Is there a way to force this to happen after the war is deployed? Otherwise each server has to wait till a wfs request comes in and it will start the catalog init process on that server. -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users