Changes to culling of idle sessions on renkulab.io

Hi Renku users! A short update on managing sessions on renkulab.io.

Quick Summary: In the default resource pool (custom resource pools are unchanged):

  • Time before an idle session is paused: 12 hours → 2 hours (new)
  • Time before a paused session is removed: 2 weeks (unchanged)

We have noticed that many sessions are left unattended for long periods of time, thus sitting idle and taking up precious resources. Since we are committed to ensure timely access to required resources and their sustainable consumption, we have decided to shorten the amount of time that we allow sessions to sit idle before pausing them.

From now on, sessions launching from the default public resource pool will be paused after two hours of inactivity (previously it was 12 hours). Inactive sessions are ones where there is no activity in the browser, and where the CPU load is below a threshold. Don’t worry, you can still resume your session later and whatever you had on disk will still be there. However, if you don’t come back to your session for more than 2 weeks, it will still be permanently removed.

To ensure that your work is preserved, either push to your git repository or attach an external storage to your project.

Note: This change ONLY applies to Renku public resource pool - if you would like to get a custom resource pool with more resources or to customize the idle time threshold, get in touch with us at hello@renku.io.