11-10-2020 09:43 AM
We have a client who needs geoprocessing capabilities in Apollo for theirs users.
They can have up to 20 concurrent users calling different geoprocesses and getting and downloading the results.
What are the feedbacks and recommendations in using WPS in such configuration?
Is there a way to create a network of processing engines behind apollo in order to serve all those users without making them wait too long for a job to finish if this is the way it works?
Also, what about the Core Geoprocessing API? Is it a way to go to well serve this type of usage?
Note that the users should be able to find source data (from the catalog) and apply the processes on them.
Thanks in advance for all the answers.
This is quite urgent since we have a meeting with the client on thursday (and tomorrow is a holiday here).
11-10-2020 04:54 PM
Normally the bottle neck is the disk I/O, I will recommend to have fast SSD for image storage directly attached to Apollo server.
You can setup Apollo adv/pro cluster (with multiple nodes & fast network connection) to do geoprocessing load balance.
Apollo essential doesn't have catalog search capability, you will need Apollo adv/pro for that.
11-12-2020 12:37 AM - edited 11-12-2020 12:54 AM
Thanks very much Haiyan,
Do you know which spatial modeler engine apollo uses?
I mean, do we need specific module and license for the nodes (aside from the apollo license)?
11-12-2020 01:24 AM
With the current APOLLO implementation, you just need to set up an APOLLO Pro on each node (one APOLLO license per node).
With the load balancer configuration, you can decide to dedicate some nodes to geoprocessing only (forward only geoprocessing requests to some nodes).
11-12-2020 01:34 AM
Thanks very much Flo.
Last question: Each node manage one request/job (process) at the time?
Or it can manage more than one in parallel depending on the resources?
11-12-2020 09:26 AM
From my understanding, One WPS job / request, one WPS job can not be splited to run on multiple nodes.