Runtime Management

Starting Container

When you open up a notebook, you are loading up all the notebooks paragraph code and output as it was last saved. Each notebook editing session starts by running a container. Each notebook session loads up an isolated computing resource which only loads an image into memory.

By running a notebook, a paragraph, or a scheduled job, you are starting up the container. This event can take a few seconds. The size of the container you are running is determined by your runtime settings. Every second that the container is running is tracked and consumes Zepl credits.

Starting a Container by Running the entire notebook end to end

Run Notebook

Clicking the Run button starts up a container executes an entire notebook end to end. Most notebooks are designed so that they can run reproducibly end to end as this allows you to run reproducible analytics for changing data sets. If anything goes wrong running a notebook end to end, your container session is still open and you can begin debugging paragraph by paragraph. You can click the Run button again at any point to run the analysis end to end.

Run Notebook button at the top of the Notebook Editor

​

Run Paragraph

Running individual paragraphs is another way of starting up the notebook container and engaging with the notebook.

Run Paragraph button at the top of two separate paragraphs

Scheduled Jobs

When you build a notebook that executes a complete process end to end, you may want to run that notebook at regular intervals. Zepl's Scheduled Jobs lets you run a notebook end to end at whatever schedule makes sense for you. You can easily schedule a job from the notebook actions. Jobs that are scheduled to run will automatically shut down the container after the last paragraph finishes executing, minimizing compute idle time.

You can learn more about creating Scheduled Jobs here:

You can learn more about managing Scheduled here:

Stop Container

Stopping the container is what stops the notebook session. When the notebook session shuts down, everything that was stored in the container memory - data, variables, etcs - will be lost. Only the notebook configuration settings and paragraphs (code and last calculated output) will be saved. This can be achieved through settings in the runtime menu

Each resource attached to the notebook also has an idle shutdown period - the default for Zepl provided resources is 30 minutes. Every time a paragraph is executed, the idle shutdown clock restarts.

Organization Owners and Infrastructure Administrators can monitor container execution in the monitor section of the product.

There is a tradeoff between setting longer resource timeout periods - it makes it easier to work in the notebook uninterrupted, but you may also have larger idle credit costs