131
edits
Socorro:Overview: Difference between revisions
→Socorro 2.x infrastructure
DEinspanjer (talk | contribs) |
DEinspanjer (talk | contribs) |
||
| Line 6: | Line 6: | ||
* Reports table(s) in Postgres -- The reports tables are partitioned by date ranges and they contain a record for every processed crash report. They are used for user searches, and for generating the materialized views that drive Socorro reports. Having this data in a traditional RDBMS means there are limitations to the amount of data that can be easily managed. | * Reports table(s) in Postgres -- The reports tables are partitioned by date ranges and they contain a record for every processed crash report. They are used for user searches, and for generating the materialized views that drive Socorro reports. Having this data in a traditional RDBMS means there are limitations to the amount of data that can be easily managed. | ||
=Socorro 2.x infrastructure= | =Socorro 2.x infrastructure= | ||
== [[Socorro:OperationalMetrics]] == | |||
==Impetus== | ==Impetus== | ||
The [[crashkill]] project became very important around the timeframe that we were planning for Firefox 3.6. The decision was made that it would be useful if we were able stop throttling and better evaluate the long tail of crash reports. Further, there were increasing requests for complex reports such as correlations that were difficult to deliver within the existing infrastructure. | The [[crashkill]] project became very important around the timeframe that we were planning for Firefox 3.6. The decision was made that it would be useful if we were able stop throttling and better evaluate the long tail of crash reports. Further, there were increasing requests for complex reports such as correlations that were difficult to deliver within the existing infrastructure. | ||