.jpg)
The complaint arrives as “the dashboard is slow”, and the first instinct is to look at the database.
Check the query time in Superset’s chart data response and it is often under a second.
The other nine seconds are in the browser: parsing the response, transforming it, and drawing a hundred thousand DOM nodes.
Custom plugins are especially prone to this because they are written against a sample dataset and shipped before anyone tries them on the real one. (If you have not built one yet, start with how to build a custom chart plugin for Apache Superset; this post assumes that structure.)
This post is about finding where the time goes and fixing it, in the order that gives the most improvement for the least rework.
No comments:
Post a Comment