<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Yes -- let's test this in as many
environments and scenarios as we can. Feel free to check out and
kick the tires and let me know how it works.<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://github.com/mdboom/mpl_browser_experiments">https://github.com/mdboom/mpl_browser_experiments</a><br>
<br>
Thanks to Jason's work to make this work in websockets and some
further tweaks today, the multi-user scenario is much improved.
The difference image is computed only once per server and then
sent out to all of the clients. So, yes, bandwidth usage
increases O(n) (where n is the number of clients), but CPU time on
the server should be relatively constant. It's conceivable that
duplicating the data to multiple clients could be handled by some
sort of multicast proxy. Obviously, if we were just able to send
transformation changes to each client, the bandwidth would be much
smaller. But that requires moving the rendering into the browser,
or at least something local that contains all of the data.<br>
<br>
Mike<br>
<br>
On 10/11/2012 11:45 PM, Brian Granger wrote:<br>
</div>
<blockquote
cite="mid:CAH4pYpSO1M94_r-he=3P_REPM4w6feYgHxE7Y7FRvUpb=JROfQ@mail.gmail.com"
type="cite">
<pre wrap="">It is not clear to me that the stream of PNGs will win in the end. If
you make a single static plot of a large data set, that is way better
than trying to send the data to the browser and rendering it there.
But if you have to send hundreds or thousands of PNGs to get
interactivity, that benefit may be washed out. Especially if you have
multiple users interacting with plots - the server could quickly grind
to a halt. I think we should do tests to see how bad it gets, taking
into account the multiple user question. The one performance benefit
that I can think of is that you can tune the level of interactivity to
limit the data that comes back. For large data sets, users might be
willing to settle for less interactivity. That option doesn't exist
when you send all the data back.
Cheers,
Brian
On Thu, Oct 11, 2012 at 2:49 PM, Michael Droettboom <a class="moz-txt-link-rfc2396E" href="mailto:mdroe@stsci.edu"><mdroe@stsci.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I have a proof-of-concept way to make interactive plots in the browser work
using transparent PNGs described here:
<a class="moz-txt-link-freetext" href="http://mdboom.github.com/blog/2012/10/11/matplotlib-in-the-browser-its-coming/">http://mdboom.github.com/blog/2012/10/11/matplotlib-in-the-browser-its-coming/</a>
No PRs yet, because this is miles from ready for that, but it would be
helpful to get some feedback about how this works in different
browsers/platforms/network environments etc.
Mike
_______________________________________________
IPython-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a>
<a class="moz-txt-link-freetext" href="http://mail.scipy.org/mailman/listinfo/ipython-dev">http://mail.scipy.org/mailman/listinfo/ipython-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>