|
Fritz Jooste Administrator Posts: 81
6/29/2015
|
Fritz JoosteAdministrator Posts: 81
A Long Running Process, or LRP, is a process that runs on the server and may take a long time to complete (several minutes to several hours). LRPs are initiated when a Deterioration Model is run, or when a data intensive Tool is being executed (e.g. Data Joins). LRPs are run on a separate thread on the server to ensure that the process is completed, and the results stored successfully, whether or not the user is still connected.
When you initiate a LRP, for example when you start a complex data join or calculate deterioration rates over many network segments, JunoViewer Web will automatically initialize a LRP. You will be notified that a LRP has started, and often you will automatically be redirected to the My Long Running Processes page. You can also manually navigate to this page by looking under the Tools menu.
While your LRP is in process, you can go and have lunch or continue working on your computer, while our powerful server will chew through your calculations. You can log off and close your browser if you want, or even shut down your computer - this does not matter since the process is running on another computer altogether. After a few minutes, or hours, depending on the size of the task, you can re-visit the My Long Running Processes page and check if the process has been completed. For many processes, the LRP will create a result file which can be automatically downloaded when the process is completed.
Why LRPs?
Some of the functionalities that are available under the Tools menu may take a long time to complete (from several minutes to several hours, depending on the size of the data set that is being processed). Data Join operations, in particular, can take several hours to complete when they are performed on large networks.
Such long running processes are problematic from a web application viewpoint, because the user may be disconnected or logged out before the process is completed. For this reason, the JunoViewer Web framework has special means for handling LRPs.
Whenever a user initiates a process that may take a long time to complete, that process is put into a queue which is checked every two minutes. Any process in the queue is then started on a separate thread on the server, which means the process will complete and store the results whether or not the user is connected.
For each user, a log is kept of any LRPs which are in process or completed. This log can be viewed on the My Running Processes page, which shows any processes which were completed during the last three days. If there is a result set associated with an LRP, then a link will be shown next to that process, and the result set can be downloaded via that link. If an error occurred during execution of an LRP, then an informative error message will be displayed where available.
edited by philip on 22/11/2016
|