jlav

Blake that is a great suggestion, in the example you sent the FPS was about 10 and after caching it jumped immediately to 60... very nice. If I get some time tonight I am definitely going to try it out. I'll have to get creative since the map I'm using allows for zooming in and out. Maybe I'll do something similar to what google used to do with maps. Cache an image and then after zooming in or out re-cache. I'm excited to test this, thanks for the suggestion!

I have been using d3.js pretty religiously on a client side browser application that provides a user the ability to interact with a node edge graph (drag/drop nodes, click on nodes & edges for details, highlight nodes & edges, etc). All of the objects on the graph as svg elements and I've notices a significant drop in performance when there are 400+ nodes on displayed. The graph has the ability to zoom, pan, and update data through async calls. I'm going to try out GSAP to see if we gain any performance and can increase the number of elements on the page. I figured I'd ask if anyone else has tried something similar just to get an idea as I head down that path. I've read several posts on the performance hit of rendering svg's and not sure if there is a way around that but I'd love to know if anyone has tried using GSAP for an interactive node/edge graph and if so what kinds of performance gains did you see.