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
I suspect this isn't heatmap-specific, but that's the context in which I'm seeing it pop up.
In a Juno Session, running
using PlotlyJS
X =rand(1025, 5000)'plot(heatmap(z=X))
I use this sort of thing for plotting audio spectrograms.
On my machine the plot line takes about 12s before it looks like the Julia function returns (I see a result in Atom and the spinner animation stops), and then 9s more before the heatmap is displayed.
Timings also seem about the same when running from the REPL.
here is a JSFiddle with a pure-javascript version.
Clicking run displays the plot in about 2.5-3s, which also isn't great, but it seems like the Javascript side isn't the main bottleneck.
I'm open to the idea that this is an unreasonable use-case for PlotlyJS, but I just like it so much for all my other plotting needs I want to use it for everything. :)
The text was updated successfully, but these errors were encountered:
Thanks for opening here. I would love to get this working more efficiently.
@MikeInnes put down some thoughts on how to do data transfer more efficiently over in #77, but I don't think anyone has taken the time to follow through.
Unfortunately I don't have a better answer for you right now :(
I suspect this isn't heatmap-specific, but that's the context in which I'm seeing it pop up.
In a Juno Session, running
I use this sort of thing for plotting audio spectrograms.
On my machine the
plot
line takes about 12s before it looks like the Julia function returns (I see a result in Atom and the spinner animation stops), and then 9s more before the heatmap is displayed.Timings also seem about the same when running from the REPL.
here is a JSFiddle with a pure-javascript version.
Clicking
run
displays the plot in about 2.5-3s, which also isn't great, but it seems like the Javascript side isn't the main bottleneck.I'm open to the idea that this is an unreasonable use-case for PlotlyJS, but I just like it so much for all my other plotting needs I want to use it for everything. :)
The text was updated successfully, but these errors were encountered: