(obviously I should create a flame graph of the code that creates the flame graph before drawing conclusions - but I digress)
Show this thread
sooooo if your flame (svg) graph gets big enough, rendering in any browser grinds to a halt. The picture below took 5 minutes to render on an i7 CPU / integrated graphics. Can't wait for more WebGL based graphs to come along C:pic.twitter.com/237mHfucaz
-
-
-
And all in all, it's amazing we can do this _at all_. Waiting a bit to get this info is well worth it, in comparison to spending hours and hours optimizing the wrong thing. But yeah, just - WebGL all the things, and especially expensive data viz things.
Show this thread -
(Footnote: I hope none of this comes off as "ohey, a particular tool isn't good" - but more like: "ohey, cool - seeing room for improvement!". Words are hard, hope it translates well!)
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.