5 ms·

@tmostak large dataset visualisation like this looks great, but one of the most appealing parts of Vega for me is interaction. It's just as easy with Vega to cr

@tmostak large dataset visualisation like this looks great, but one of the most appealing parts of Vega for me is interaction. It's just as easy with Vega to create composite interactions for filtering and navigating data as it is to visualise it. Is there any scope for this type of architecture to support more than just serving rendered PNGs? (Can it do that at 60fps? :P)

lmeyerov 9y ago
We separated the analytics from rendering at Graphistry, connecting GPUs on both ends. You'll notice most of their visualizations aren't showing much geometry in the client: Leveraging that, we aim for 15fps+ on datasets 100X+ bigger than normal stuff in browsers, and soon, even more. And we're looking into including MapD as part of our backend GPU analytics stack... so, yes! And if you're into visualization engineering like that, we're hiring :)
tmostak 9y ago
We've considered video rendering using the H264 encoders on the GPU, another approach might be to create a format that has all info needed for interactions and that could be deciphered on the frontend (i.e in WebGL). So it's something we're definitely looking at. We already do provide some support for hover interactions in our charting library on top of Vega, but it would be nicer to do this in Vega. Right now customers still get a lot of value from server-side rendering simply bc we can render visualizations of billions of records interactively and in real time, which is difficult or impossible to achieve in other platforms without some sort of pre-computation.
- jarmitage 9y ago
  Thanks for your reply, and yes I can imagine your tools are already very useful. Are there any examples of real-time online? It would be interesting to see what your SoTA is!
  - tmostak 9y ago
    We do support real-time ingest (helped by the fact that we do not need to index on insert). The only example we have online of that now is our Tweetmap demo (https://www.mapd.com/demos/tweetmap/ https://www.mapd.com/demos/tweetmap/)

lmeyerov 9y ago

We separated the analytics from rendering at Graphistry, connecting GPUs on both ends. You'll notice most of their visualizations aren't showing much geometry in the client: Leveraging that, we aim for 15fps+ on datasets 100X+ bigger than normal stuff in browsers, and soon, even more. And we're looking into including MapD as part of our backend GPU analytics stack... so, yes! And if you're into visualization engineering like that, we're hiring :)

tmostak 9y ago

We've considered video rendering using the H264 encoders on the GPU, another approach might be to create a format that has all info needed for interactions and that could be deciphered on the frontend (i.e in WebGL). So it's something we're definitely looking at. We already do provide some support for hover interactions in our charting library on top of Vega, but it would be nicer to do this in Vega. Right now customers still get a lot of value from server-side rendering simply bc we can render visualizations of billions of records interactively and in real time, which is difficult or impossible to achieve in other platforms without some sort of pre-computation.

jarmitage 9y ago
Thanks for your reply, and yes I can imagine your tools are already very useful. Are there any examples of real-time online? It would be interesting to see what your SoTA is!
- tmostak 9y ago
  We do support real-time ingest (helped by the fact that we do not need to index on insert). The only example we have online of that now is our Tweetmap demo (https://www.mapd.com/demos/tweetmap/ https://www.mapd.com/demos/tweetmap/)