Closed
Bug 527259
Opened 16 years ago
Closed 16 years ago
increase all the crash-stats top 100 lists to top 200 or top 300
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: chofmann, Unassigned)
Details
(Whiteboard: [crashkill-metrics])
Attachments
(1 file)
|
2.71 KB,
patch
|
ryansnyder
:
review+
|
Details | Diff | Splinter Review |
I think we have a bug on this bug filing to make sure this doesn't fall off the radar. notes below from a breakpad IRC converstation we had yesterday.
we need to try and up all top 100 lists to top 200 if we can survive the change without big impact on performance or disc space.
<chofmann> now that we have more people looking at crashes we are drilling down deeper into the lists
<chofmann> used to be we could only cover the top 20 or 30, but now we have bugs covering a big pct. of the top 100
<chofmann> bumping to 200 would increase the visibility of more crashers
<chofmann> you can see there is a inflection point around the top 300 where crash volume starts to flatten
<chofmann> https://bug524507.bugzilla.mozilla.org/attachment.cgi?id=408460
<chofmann> it would be good to get "top" reports ranking out that far, but I'd settle for 150 or 200 for now.
<chofmann> these top crash lists are the pages where we get lots of community leverage in helping to file bugs and analyze the crash signatures
<chofmann> also, can those reports get the bugzilla id column?
<chofmann> no bug associated with a signature means an opportunity for someone to get involved ;-)
<chofmann> you can see here that we have a scattering of bugs file all the way through the top 100 on the 3.6 beta
<chofmann> http://crash-stats.mozilla.com/query/query?product=Firefox&version=Firefox%3A3.6b1&date=&range_value=1&range_unit=weeks&query_search=signature&query_type=exact&query=&do_query=1
<chofmann> sometimes bugs down in the top 50-200 are going to be easier to analyze and get fixed that long standing and hairy problems in the top 50.
<chofmann> there are good opportunities to drive crash rates lower if we expose info about those crashes on crash-stats
<chofmann> ozten / morgamic, think we could make this change to bump the topcrash lists out to 200?
<morgamic> yes
<chofmann> that would be really cool
<morgamic> yea it would be
| Reporter | ||
Updated•16 years ago
|
Whiteboard: [crashkill-metrics]
Comment 1•16 years ago
|
||
Adds two new config values
byversion_limit and bybranch_limit
which are both set to 200 now.
Attachment #411203 -
Flags: review?
Updated•16 years ago
|
Attachment #411203 -
Flags: review? → review?(ryan)
Comment 2•16 years ago
|
||
Comment on attachment 411203 [details] [diff] [review]
Adds config for top crashers limit and bumps it to 200
Looks good!
Attachment #411203 -
Flags: review?(ryan) → review+
Comment 3•16 years ago
|
||
In topcrashbysig added two new config values byversion_limit and bybranch_limit
which are bumbed to 200.
r1438
On stage in 5-10 minutes.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•14 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•