If a given computation requires a large number of CPUs or memory (RAM), it is possible to scale the application to a dedicated high-performance compute node. In this case, the same application will launch with the exact same interface, however, the available resources can be significantly larger (e.g. up to 120 vCPU and 456GB memory) or can include additional devices (e.g. a GPU).
Application scaling is charged against the credits of the underlying account and is directly based on the amount of application runtime. Please turn off the scaled application if you no longer require the larger resources and relaunch it without scaling when the baseline resources are sufficient (e.g. investigating outputs).
For long-running jobs, you can also rely on the **** automated inactivity stopper to handle application stops. The automated inactivity stopper will shut down the application if it is not using at least half of a single vCPU for computation and it is not opened in Nuvolos for at least 6 hours.
Scaling can be done inside Nuvolos by hovering on the application icon once it has been launched and clicking the 'Scale' button. High-performance computing integration needs to be enabled for this to be possible, please reach out to support using Intercom or by e-mail if you require assistance with this.
Scaling your application
For Rstudio we recommend using the 'Local Jobs' feature to run the jobs in the background, this way you can submit multiple jobs whilst also making sure the job continues to run if you navigate away from Rstudio, without blocking the interface.
If running notebooks via Jupyter, we recommend submitting the notebooks for computation using papermill and specifying an explicit logfile when executing from the Jupyter terminal. This way you can disconnect from the Jupyter application and the notebook execution can continue whilst be able to monitor run progress.
papermill --stdout-file /files/my_job.out --stderr-file /files/my_job.err NOTEBOOK_PATH [OUTPUT_PATH]
pp = parpool('local');
The pool will be deleted after 30 minutes of idle time or with an application restart. To delete it manually, use