Is it possible to have ipython notebooks of the same Jupyter Notebook server built on one kernel?
nju08e...@gmail.com
We know, currently, when we start a Jupyter Notebook App, and create a notebook from the App GUI, then a kernel will be started, if we create more notebooks from the same App GUI( usually the URL is hostname:port) , then the same amount of kernels will be started. Do we have a configuration parameter to let these notebooks work on only one kernel, or it's just designed by Jupyter Notebook that, each notebook corresponds to one kernel, that fact that can not be changed?
If that's the fact, do we have a way to set the limitated number of started kernels of a Jupyter Notebook App ?
Seek for your help, and thanks in advance.
MinRK
There is a bit of complicated terminology, in terms of what’s technically possible and what is just a choice made in the current application, and at what level.
In general:
- It is a design choice of the existing notebook (javascript-side client) web application that each notebook has its own kernel.
- It is not a technical limitation of the APIs, and other web applications can use the same notebook javascript to build different models, where e.g. all notebooks use the same kernel, or other options.
- A lot of the notebook UI has this assumption built in, so UI would need to change substantially to support different relationships of notebooks to kernels.
- For this reason, it is not configurable in the existing application to support additional relationships between notebooks and kernels.
So it is more a UI question than anything else. Technically, any relationship of notebooks to kernels is possible. The simplest example is using a single kernel for all notebooks, since that doesn’t need any UI at all, since it doesn’t present additional choices. Another no-choice option is to run a single kernel of any given language. If you want to do something like “launch this notebook attached to the kernel of this other notebook”, then that choice must be presented in UI, which is a tricky proposition, but might be a great experiment to try as a plugin for the new JupyterLab code, which should support extension in this way much better than the 4.x JavaScript client.
-MinRK
--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/935febdc-4c42-4434-b4d7-53df2aeb4175%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.