Most charts rerequest data on each reload. This introduces a performance hit.
When the dashboard adds better time-range snapping, more opportunities for caching arise. Can we introduce a data caching layer, similar to how e.g. field-lists are cached or map tiles are cached?
How data is exactly cached is reliant on how Dashboards are currently using the bsearch layer . e.g. http-based caching may prove to more difficult when using bsearch to batch calls.
Most charts rerequest data on each reload. This introduces a performance hit.
When the dashboard adds better time-range snapping, more opportunities for caching arise. Can we introduce a data caching layer, similar to how e.g. field-lists are cached or map tiles are cached?
How data is exactly cached is reliant on how Dashboards are currently using the bsearch layer . e.g. http-based caching may prove to more difficult when using bsearch to batch calls.