5 ms·

What’s the advantage of this? It isn’t obvious to me that reducing memory usage and CPU of an empty/idle kernel is all that meaningful if the actual Python code

by oivey 2y ago

What’s the advantage of this? It isn’t obvious to me that reducing memory usage and CPU of an empty/idle kernel is all that meaningful if the actual Python code in your notebook uses far more resources. It’s also not obvious to me how Go’s better threading helps, either, if all the computational bits are in Python anyway.

energy123 2y ago
I have one nit with JupyterLab. When I press Ctrl+F, it takes ~0.4 seconds for the search box to open, and sometimes the first keystroke doesn't register when I type something into that search box. "Zasper ... provides ... exceptional speed". If they can just make input latency indistinguishable from vim, that's a very worthwhile value add.
lf-non 2y ago
It is quite beneficial for people who aren't writing python. And for them managing jupyterlab installations is a bit of pain. I would like to use this with xeus kernel for sql (which is also native) and if this reduces the resource consumption of that setup significantly, its a big plus for me.
- oivey 2y ago
  The README says the savings is ~75 MB. In most notebook workflows you’re at most running a couple at once. Saving <1% of my system memory doesn’t let me do anything I couldn’t do before. This also isn’t going to add concurrency/parallelism to your SQL unless xeus has some special magic that this is somehow able to exploit.
  - lf-non 2y ago
    I was primarily talking in the context of shared server deployments for teams
- BiteCode_dev 2y ago
  uvx --from jupyter helps with that significantly.
em500 2y ago
Yes, the problem with such projects is that the must be very clear benefits for users (rather than developers) to attract a critical mass. At work we had Apache Zeppelin running on the servers alongside with Jupyther. In practice almost nobody used it (probably because almost nobody else used it, so if yourun into any issues you're on your own), so it was quietly shelved after a few years.

by oivey 2y ago

energy123 2y ago

I have one nit with JupyterLab. When I press Ctrl+F, it takes ~0.4 seconds for the search box to open, and sometimes the first keystroke doesn't register when I type something into that search box. "Zasper ... provides ... exceptional speed". If they can just make input latency indistinguishable from vim, that's a very worthwhile value add.

lf-non 2y ago

It is quite beneficial for people who aren't writing python. And for them managing jupyterlab installations is a bit of pain. I would like to use this with xeus kernel for sql (which is also native) and if this reduces the resource consumption of that setup significantly, its a big plus for me.

oivey 2y ago
The README says the savings is ~75 MB. In most notebook workflows you’re at most running a couple at once. Saving <1% of my system memory doesn’t let me do anything I couldn’t do before. This also isn’t going to add concurrency/parallelism to your SQL unless xeus has some special magic that this is somehow able to exploit.
- lf-non 2y ago
  I was primarily talking in the context of shared server deployments for teams
BiteCode_dev 2y ago
uvx --from jupyter helps with that significantly.

em500 2y ago

Yes, the problem with such projects is that the must be very clear benefits for users (rather than developers) to attract a critical mass. At work we had Apache Zeppelin running on the servers alongside with Jupyther. In practice almost nobody used it (probably because almost nobody else used it, so if yourun into any issues you're on your own), so it was quietly shelved after a few years.