Closed Bug 823641 Opened 12 years ago Closed 10 years ago

Enable Dark Matter Detector on Daily builds (memory)

Categories

(Thunderbird :: Build Config, defect)

20 Branch
x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mconley, Unassigned)

References

Details

According to https://wiki.mozilla.org/Performance/MemShrink/DMD, the Dark Matter Detector allows Gecko apps to drill down and see what the "heap unclassified" memory allocations are all about. Is this something we want to activate on Daily builds, like we do with profiling?
Blocks: 823573
(In reply to Mike Conley (:mconley) from comment #0) > Is this something we want to activate on Daily builds, like we do with > profiling? Is Mark the right person to answer? I don't know enough about DMD to know if or how it will help us.
Flags: needinfo?(mbanner)
Firefox doesn't seem to activate this by default, even on Daily. So I'd probably start with asking why they don't. Also, this I'd view this as a community decision to be discussed on tb-planning.
Flags: needinfo?(mbanner)
(In reply to Mark Banner (:standard8) from comment #2) > Firefox doesn't seem to activate this by default, even on Daily. So I'd > probably start with asking why they don't. perhaps because of bugs like bug 819839 and bug 827283? njn ? > Also, this I'd view this as a community decision to be discussed on > tb-planning. good point
Flags: needinfo?(n.nethercote)
Is anybody actively working on adding memory reporters for Thunderbird, or seeing what kinds of things result in high heap-unclassified in about:memory? If not, I don't think any performance hit from this (I don't know how bad it is, but it is certainly much worse than enabling profiling) would be worthwhile, because nobody is going to make use of the results. In Firefox, most heap-unclassified problems go like "I get high heap-unclassified on this page", so it is easy enough to just reproduce user-reported issues in a special profiling build.
You can build with --enable-dmd and then run without DMD enabled (i.e., without setting DMD=1). In that case, I'd expect the overhead of DMD to be relatively small. But I agree with everything Andrew said.
The slowdown is small but noticeable, and it's not of wide enough interest and usability for it to be worth turning on for Daily users, IMO.
Flags: needinfo?(n.nethercote)
(In reply to Nicholas Nethercote [:njn] from comment #6) > The slowdown is small but noticeable, and it's not of wide enough interest > and usability for it to be worth turning on for Daily users, IMO. is this an actual assessment of you having used it in Thunderbird?
Flags: needinfo?(n.nethercote)
(In reply to Andrew McCreight [:mccr8] from comment #4) > Is anybody actively working on adding memory reporters for Thunderbird, yes (In reply to Andrew McCreight [:mccr8] from comment #4) > In Firefox, most heap-unclassified problems go like "I get high > heap-unclassified on this page", so it is easy enough to just reproduce > user-reported issues in a special profiling build. I'm not sure this reasoning, "reproduction is normally easy", applies to Thunderbird. Often, only the user can reproduce a crash or other type of problem. Also, Thunderbird is new to the memory analysis game, and could benefit from a period of making analysis as easy as possible. So if the hit of DMD is minimal/not noticeable to the user I'd say it's worth enabling it nightly just so we don't have to hassle of making special builds when we want to test a problem.
> is this an actual assessment of you having used it in Thunderbird? I haven't tried it on Thunderbird. Have you? I'm confident that the effects it has on Firefox will be similar to the effects on Thunderbird, because it slows down malloc/free and both apps, like most apps, use those operations frequently. DMD slows things down. It doesn't work properly on Windows (bug 819839) and Android (bug 823354). If you can live with that and you think the benefit outweighs the costs, then by all means turn it on.
Flags: needinfo?(n.nethercote)
mconley, given the assessments above show we close this wontfix for now? I'm happy to get what I need for bug 805023 via special builds
Flags: needinfo?(mconley)
Summary: Enable Dark Matter Detector on Daily builds → Enable Dark Matter Detector on Daily builds (memory)
See Also: → 805023
(In reply to Wayne Mery (:wsmwk) from comment #10) > mconley, given the assessments above show we close this wontfix for now? > Yep.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(mconley)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.