Long-running applications
Nuvolos supports long-running applications whilst attempting to automatically stop applications which are no longer required to run.
Last updated
Nuvolos supports long-running applications whilst attempting to automatically stop applications which are no longer required to run.
Last updated
Nuvolos aims to provide the maximal resources for applications that require it, whilst freeing up resources from unused applications to optimize organization resource usage. As described below, we provide convenient default policies that:
Allow long running computations to finish without user interaction
Stop inactive applications, to free up resources for other organization members / minimize credit usage
We achieve the above through our automatic inactivity stopper as described below.
For certain applications such as RStudio, long-running computations are best done using specific features off the app (e.g. RStudio jobs). Please take a look at the application-specific guides as well.
In order to efficiently allocate resources, Nuvolos automatically stops inactive applications. Research and Education spaces are handled differently.
For research spaces Nuvolos considers an application being active if either:
It is actively opened on Nuvolos
It is actively computing (using more than half of a single virtual CPU)
In research-purpose spaces, there can be two types of applications: applications with dedicated resources (a.k.a. "scaled apps") and applications without dedicated resources (a.k.a. "unscaled apps"). the default inactivity limit is six hours for unscaled apps and one hour for scaled apps.
For unscaled apps, the inactivity limit can be set between 1 hour and 24 hours by space administrators, at the applications configuration menu. This has no effect on scaled applications.
Researchers can launch long running computations and their application will keep running until actively computing. If the computation is finished (either due to completion or an error) and the application is not opened on Nuvolos, it will be auto-stopped. We therefore recommend explicitly capturing and saving output logs to ensure that any warnings or errors are captured.
For education spaces the application is only considered active if it is actively opened on Nuvolos, unattended long-running computations will be automatically terminated.
In education-purpose spaces, the default inactivity limit is one hour.
To keep an application active in an education space, you need to make sure that the application is in focus in your browser for more than one (uninterrupted) minute every hour.
