Although the ECO dashboard currently uses up less RAM than the HHS and FMA dashboards, it has twice the CPU and network usage. This may be due to the instant plot updates as the user changes geography and display settings. Some considerations:
A "generate plot" button so that the plotting code runs only when the button is clicked after the user is happy with the settings.
Caching plot images (RAM seems to not be an issue so why not?)
(hard) Code optimization. Ideally should not need this.
Although the ECO dashboard currently uses up less RAM than the HHS and FMA dashboards, it has twice the CPU and network usage. This may be due to the instant plot updates as the user changes geography and display settings. Some considerations: