{"id":5178,"date":"2012-02-21T16:21:31","date_gmt":"2012-02-21T23:21:31","guid":{"rendered":"http:\/\/blog.mozilla.org\/metrics\/?p=5178"},"modified":"2019-09-18T12:05:34","modified_gmt":"2019-09-18T19:05:34","slug":"sampling-crash-volumes-rates-and-rarity-for-socorro-samples","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/metrics\/2012\/02\/21\/sampling-crash-volumes-rates-and-rarity-for-socorro-samples\/","title":{"rendered":"Sampling Crash Volumes, Rates and Rarity for Socorro Samples"},"content":{"rendered":"

1\u00a0Introduction<\/h3>\n
\n

The Socorro crash report accumulation pipeline does not process all the crash reports. Though every report is stored on disk, only 10% are processed and saved in HBase as JSON objects. Each crash report has a crash signature (Crash Report Signature or CRS for short). The relationship between crash reports and CRSs is many to one.<\/p>\n

Consumers of the crash reports (engineers working on bugfixes, product managers to name a few) had concerns regarding the use of samples. For example, some asked if the 10% sampling is a viable sampling rate to accurately estimate the frequency of the CRSs and if not all of them, then how accurate are the top N most frequently observed crash report signatures? With FF’s usage running into the 100 millions, we can expect new CRSs to be coming in every day. Some are very rare (occurs for a small user base) and others more frequent. How many days can we expect to wait till we see 50% of all the CRS that come in (for a given version)?<\/p>\n

To answer these questions, the #breakpad team processed every crash report for the week 03\/22-29\/2011 , post Firefox 4 release. This served as a full enumeration of the crash report data. The full enumeration contained 2.2MM crash reports belonging to 84,760 CRSs.<\/p>\n

Primarily, the crash-stats dashboard lists the top 100 most frequent crashes by OS. Some questions,<\/p>\n