Improve viewer performance to better handle large result sets

[ghostwords]

Once you get into tens of thousands of URLs, the viewer starts taking too long to render results.

The backend becomes slow/starts using a lot of RAM (bad, but OK for a single-user app) and the results page gets too big to render in a reasonable amount of time (much worse since it makes the viewer unusable past a certain point).

[cooperq]

I would say that we need to be able to handle about 100,000 domains. Here are some links that might be useful:
http://w2ui.com/web/blog/7/JavaScript-Grid-with-One-Million-Records
http://misoproject.com/dataset/

[ghostwords]

Viewer redesign plan:

• The list of crawls goes away, at least in its current form as the front page.
• The results screen becomes the front page, with search filters expanded to include the list of crawls.
• The results will no longer show script-level data. All data will get collapsed to domain level.
• The results page will probably be a dynamically-rendered, sortable table. Loading visible rows only (occlusion rendering?) is like pagination 2.0: performance w/o the extra burden of pagination controls.
• There will be a new domain detail report page, reachable from the main results page. This page will present script-level findings and provide additional information such as exact properties accessed, etc.