Incidentally, the automatic regression detection dashboard has been
coming together recently with Perfherder, which should let you track
such things as this much more easily (as well as providing a convenient
interface for filing bugs). For example, you can see all recently
detected regressions and improvements in memory usage here:
https://treeherder.allizom.org/perf.html#/alerts?status=-1&framework=4
(there's some false positives in there I know, we could probably do with
some slightly better regression-detection code...)
More updates soon.
Will
On 2016-02-09 5:25 PM, Mark Finkle wrote:
Hi All,
Recently Geoff Brown landed an AWSY-like system [1] for tracking memory
usage on Perfherder. This is awesome. It's one of my pinned tabs.
I was happy to see two recent "drops" in memory usage:
1. A ~3% drop in "Resident Memory Tabs closed [+30s]", likely due to Bug
990916 which expires displayports
https://treeherder.mozilla.org/perf.html#/graphs?series=[mozilla-inbound,f9cdadf297fd409c043e8114ed0fa656334e7fad,1]&zoom=1454516622714.927,1454583882842.8733,181623181.32925725,250028978.43070653
2. A ~2% drop across all memory tracking sometime on Feb8. Hard to pick a
changeset, but the drop happened when inbound was merged to fx-team.
https://treeherder.mozilla.org/perf.html#/graphs?series=%5Bmozilla-inbound,f9cdadf297fd409c043e8114ed0fa656334e7fad,1%5D
Great to see drops in memory usage!
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1233220
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
