Hi,
As far as I know it is exactly a frontend to REST API.
If the CPU cycles which are consumed for handling the protocol are meaningful then you probably want to start a very large number of processes which are very fast to perform. For me REST means something like start seeding (< 1 second) and then just seed (> many hours).
-Jukka Rahkonen-
Gregory Lewis-Paley wrote:
Is the GWC seed page simply a web frontend for the REST API of Geoserver?
Is there another option for submitting requests to the underlying GWC/Geoserve?
I have some scripts that need to whack away at a local Geoserver instance with the REST api but I've come to the conclusion it is leaving lots of performance on the floor. I suspect it's related to the entire network/REST protocol stack taking a significant portion of the CPU cycles.
Greg
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
That's interesting about starting a very large number of small jobs. That is actually something I'm trying to avoid as I figured it would overwhelm Geoserver REST handling and the queues...
Right now I have it starting a mix of small (1s) and large (many hr) jobs. Some local tests I've done started the same seed job as a single job and also many different size jobs, submitted all at once. I found about half the tiling performance with the multi-job approach. I'm using the multi-job approach as the areas I will be seeding are oddly shaped and don't fit with a nice single bounding box.
On 16-04-18 08:43 PM, Rahkonen Jukka (MML) wrote:
Hi,
As far as I know it is exactly a frontend to REST API.
If the CPU cycles which are consumed for handling the protocol are meaningful then you probably want to start a very large number of processes which are very fast to perform. For me REST means something like start seeding (< 1 second) and then just seed (> many hours).
-Jukka Rahkonen-
Gregory Lewis-Paley wrote:
Is the GWC seed page simply a web frontend for the REST API of Geoserver?
Is there another option for submitting requests to the underlying GWC/Geoserve?
I have some scripts that need to whack away at a local Geoserver instance with the REST api but I've come to the conclusion it is leaving lots of performance on the floor. I suspect it's related to the entire network/REST protocol stack taking a significant portion of the CPU cycles.
Greg
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users