Toggle To Keep Runtime Environments Running While Not Connected to Internet

Post author
Alexander Genshaft

Currently, it seems that runtime environments pause if they are not getting feedback from the source computer. While this is a feature to many as it enables people to not be charged for runtime environments they forget about (well, at least the active RAM), it also hinders those that may have longrunning jobs and would like to commute home, get on a flight, etc. 

Would it be possible to create a toggle button or something like that to indicate which preference I would like for a specific runtime environment? Better yet, a button for the current state, so when we do walk away from our computers and shut them, we can indicate our preference then, rather than at the start of the runtime session?

Comments

4 comments

  • Comment author
    Jason Cerrato
    • Official comment

    Hi all,

    I'm happy to report that you now have explicit control of your autopause timer in the Cloud Environment configuration panel!

    Kind regards,

    Jason

  • Comment author
    Mahdiar Sadeghi

    If we are not going to have this feature, what would be best way to run analysis offline? Should convert the notebook to a workflow? Just wondering, as I am dealing with the same problem.

    0
  • Comment author
    Sushma Chaluvadi

    Hello Mahdiar and Alexander,

    Currently the runtime will not auto-pause if kernel is active. However, if your notebook is not connected to a browser, the results of your run would not be print out in the notebook so you can and will need to write the outputs out to a file if you want to keep them. 

    The details of all auto-pause in kernels is described under "Kernel activity prevents auto-pause" section of this article.

    Please let us know if this is not the information you were looking for!

    0
  • Comment author
    Adrian

    I'm adding this additional context from Matt Bookman here, which seems relevant to this topic:

    It would also be nice if users had more control over behavior of the VMs. I was thinking about this same issue in the context of a few different desired user experiences:

    1. I have a laptop and I want to kick off a long-running notebook; as soon as I kick off the notebook I want to close my laptop and drive into the office.
    2. I have a laptop and I want my notebooks to pause and my notebook VM to pause when I close the laptop and drive home.
    3. I have a workstation (which is always running) and I want to be able to leave my browser open and have my VM auto pause
    4. I have a workstation (which is always running) and I want to be able to leave my browser open and have my notebooks keep running

    Today, #2 and #4 are the observed behaviors. #4 surprised a few people as they didn't realize their notebook VM just kept running (overnight, over the weekend...)

    My ideal situation would be to have the control to explicitly state my intention; do I want my notebook to be long running or do I want "idleness" to be more aggressively detected. If I do accidentally leave a browser tab open to a notebook - it would be great if there was some other avenue in which I could be informed that my VM is running and has been running for [time].

    0

Please sign in to leave a comment.