-
Notifications
You must be signed in to change notification settings - Fork 32
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
Make it possible to work without starting kaleido #52
Comments
Nice find @waralex - on the Python side we do two things that look different from this: |
Some timing results: Without auto-start kaleido, PlotlyBase needs to precompile
Without auto-start kaleido, PlotlyBase already precompiled
With auto-start kaleido, PlotlyBase needs to precompile
With auto-start kaleido, PlotlyBase already precompiled
With auto-start kaleido (async), PlotlyBase needs to be precompiled
With autto-start kaleido (async), PlotlyBase already precompiled
From what I see here, my vote would be to leave the auto start Kaleido, but to have it launch async. Any objections? |
One more set of timing:
If we are running a script to load, plot, savefig it doesn't seem to matter which option we choose |
@sglyon Are you sure that it is necessary in |
It isn't necessary. I would be willing to move this over |
The problem is not only in the launch time. By itself, starting a process that is most likely not needed by the user is not very good, IMHO. |
I want to come back to this topic. I suddenly realised that savefig was not working anymore and finally found out why. While I can understand all the arguments above, I'm missing the possibility to save figures with a small footprint. Loading the full PlotlyJS with heavy dependencies like I'd propose to define an abstract type I'd even propose to use FileIO and to define a new save method import FileIO.save
function save(io, p:AbstractPlot) [...] and keeping @sglyon What do you think? |
I have published PlotlySave.jl on my GitHub and created branches hh-abstractplot for my forks of |
The launch of kaleido (
_start_kaleido_process
call) takes quite a long time, and it is not always necessary. For example,Dash.jl
usesPlotlyBase
only to generate json forPlotlyGraph
objects. But at the same time, the launch of kaledio takes 90 percent of the time ofusing Dash
(about 2.5 seconds on my laptop).It would be really great if it could be avoided.
The options that I see are:
PlotlyJS.jl
Perhaps there are other options
The text was updated successfully, but these errors were encountered: