Custom Query (15318 matches)
Results (16 - 18 of 15318)
|#1630||implemented||Extend database schema by materialized views||Karsten||karsten|
The current database schema in ERNIE consists of tables and views. In order to support ad-hoc queries for dynamic graphs, we need to have materialized views plus a good concept to keep them updated. Update strategies range from (1) periodically re-generating the whole materialized views, (2) collecting changes on base tables and updating only those parts of materialized views that might have changed, and (3) triggering materialized view changes from table changes. While (1) is easiest to implement, it's infeasible for the amount of data in the database. (2) and (3) are harder to implement, but better fit the use case of having data covering multiple years in the database and adding data covering an hour or two. (2) is probably more efficient than (3), but even harder to implement. Kevin is working on this and might have results in July 2010.
|#1631||implemented||Extend dynamic metrics portal prototype to all graphs||Karsten||karsten|
The dynamic metrics portal prototype consists of a website with a form to choose the graph to display and a servlet that calls R to generate the requested graph. The prototype works for graphs on network size only and is still a bit rough around the edges. When extending the prototype to other graphs, also unify their size to 0.75 and place the legend at the top.
|#1632||implemented||Make Data page dynamic||Karsten||karsten|
The Data page in the Metrics Portal (http://metrics.torproject.org/data.html) lists all metrics data that we have. This page is a static HTML page that is updated whenever we have new data. This means we need to update it at least once a month to list the new monthly descriptor tarballs. Once we switched the Metrics Portal to JSP/Servlets, this page should be generated dynamically with whatever data is available.