You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to d3...@googlegroups.com
Hello, I was planning on learning d3js for a project I'm working on. However, it appears some visualizations are so painfully slow on the iPad (and probably other mobile platforms) that it is definitely a show stopper for us.
So before investing time and effort in learning d3.js I was wondering how people were dealing with this performance issue. More specifically, I was wondering if people had tried solutions like web workers, or forcing hardware acceleration ?
Thanks
Kai Chang
unread,
Sep 18, 2012, 4:40:36 PM9/18/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to d3...@googlegroups.com
Web workers probably won't help.
CSS 3d transforms do help for DOM transitions. For many elements,
rendering with Canvas rather than SVG helps considerably.
D3 itself is quite fast. It's the SVG rendering and DOM manipulation
that is slow.
Bart Czernicki
unread,
Oct 5, 2012, 3:40:12 PM10/5/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to d3...@googlegroups.com
So..what version of the iPad? I haved tested d3.js with most of the examples and they work OK..heavy interactivity degrades performance.
D3.js (in a production environment) will need a fast/lightweight access to the data usually with a RESTful JSON data service-like API and the graphing portion itself. On a mobile device there are many ways to optimize this type of "design/architecture" and thus far I have not run into many problems as long as you keep things like sliders/animations/tons of nodes to a minimum.