SummerOfCode/2013/newMemoryPage/week9

End of Week 9: Report

It seems that our last week's attempts at introducing live updates into the page were a bit hurried, and our conclusions on seeing the initial few data-pushes working, foregone. The data looks like it is stacking up on the page, and the problem could be because

• The GC engine is being overwhelmed, or
• New data is being added alongside, instead of replacing, the old data

Either of these problems are relatively easy to fix, but the big problem is that it does not look like either one of them are the culprits here. We have tried manually flushing the HTML holders for the data, even that doesn't seem to work.

It seems that we need to break down the page into a number of groups (which, to anyone reading this, is good D3 practice), and take it from there.

EDIT: The issue, after being resolved (by tearing down the page and starting from scratch), was resolved in hindsight. It would seem that the reason for the apparent overflow was the failure to flush the numbers from the holder in the main.js script, which caused the inflated values to be seen on the page. We still don't know what caused the apparent slowdown of the browser after the few pushes, but the new approach seems to work fine, so we won't go there. For now.