Thanks to visit codestin.com
Credit goes to github.com

Skip to content

use new binary comm in nbagg #4382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tacaswell opened this issue Apr 26, 2015 · 2 comments · Fixed by #18583
Closed

use new binary comm in nbagg #4382

tacaswell opened this issue Apr 26, 2015 · 2 comments · Fixed by #18583
Milestone

Comments

@tacaswell
Copy link
Member

A recent PR (ipython/ipython#7757) into IPython adds binary comms so that we do not have to launder pngs through a base64 encoding to communicate with the JS side.

We should look into using the binary comms to see if we can get a bit more performance out of nbagg.

Not sure on what timeline we should aim for here as this is not in a released version of IPython/Jupyter (as of 2015-04).

attn @pelson

@tacaswell tacaswell added this to the proposed next point release milestone Apr 26, 2015
@OceanWolf
Copy link
Member

This may have a slight effect on MEP27, I didn't touch binary comms directly in WebAgg, but I made a new wrapper around it. That said, I have yet to touch NbAgg, so I have no clue how that works compared with WebAgg. Anyway, I will make WebAgg my first priority after the base MEP27 branch lands.

@pelson
Copy link
Member

pelson commented May 5, 2015

Thanks @tacaswell - yes, this looks really interesting. 👍

@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.2 (next next feature release) Oct 3, 2017
QuLogic added a commit to QuLogic/matplotlib that referenced this issue Sep 25, 2020
@QuLogic QuLogic modified the milestones: needs sorting, v3.4.0 Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants