Currently, the correlation page uses the EXTREMELY hacky method of converting the entire matched networks object returned from the database to JSON and injecting it into the global javaScript scope of the page. This means that extra bytes are transported for every single extra attribute that we don't care about as well as all of the json structure which then has to be parsed into an object and stored in memory by the client.
A much better solution would be to create a background page that retrieves one attribute from multiple networks and maybe even converted it into a data format that highcharts can understand, keeping as much as the workload server-side as possible.
Currently, the correlation page uses the EXTREMELY hacky method of converting the entire matched networks object returned from the database to JSON and injecting it into the global javaScript scope of the page. This means that extra bytes are transported for every single extra attribute that we don't care about as well as all of the json structure which then has to be parsed into an object and stored in memory by the client.
A much better solution would be to create a background page that retrieves one attribute from multiple networks and maybe even converted it into a data format that highcharts can understand, keeping as much as the workload server-side as possible.