You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In JupyterLab or Jupuyterlite, we may have several notebooks open in different JupyterLab panels, and each of these notebooks may want a database?
Also, if we are using notebook rather than JupyterLab, each separate notebook will be running in its own tab. Once again, what are advantages and disadvantage of using a worker? Indeed, would a worked be necessary? What if different notebooks want to access the same database, from their own panel in the same JuptyerLab environment, or from separate notebook browser tabs? Or what if each notebook was accessing a different database? Should it haves its own worker? I think we could start different databases by options, so is the worker just there to keep down the number of threads?
The text was updated successfully, but these errors were encountered:
pglite
has support for a multi-tab webworker. Would this make sense?In JupyterLab or Jupuyterlite, we may have several notebooks open in different JupyterLab panels, and each of these notebooks may want a database?
Also, if we are using notebook rather than JupyterLab, each separate notebook will be running in its own tab. Once again, what are advantages and disadvantage of using a worker? Indeed, would a worked be necessary? What if different notebooks want to access the same database, from their own panel in the same JuptyerLab environment, or from separate notebook browser tabs? Or what if each notebook was accessing a different database? Should it haves its own worker? I think we could start different databases by options, so is the worker just there to keep down the number of threads?
The text was updated successfully, but these errors were encountered: