ABSTRACT
Large data means different things to different people at different time periods. Build time can be classified as the time it takes for the object to be serialized as JSON/HTML, whereas run time is the time it takes for the browser to render the HTML into a webpage. In the case of plotly, there are two quick and easy things the readers can do to improve run time performance in any context: toWebGL() and partial_bundle(). Since latency in interactive graphics is known to make exploratory data analysis a more challenging task, systems that optimize run over build performance are typically preferable. These two options may improve runtime performance without much of any thinking, but sometimes it’s worth being more thoughtful about the readers' visualization strategy by leveraging summaries as well as being more explicit about how a graph responds to changes in the underlying data.
