We have detected an awsy regression from push: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=8194cd1a678d12095c9b4906a5eb776306c47b7e As author of one of the patches included in that push, we need your help to address this regression. Regressions: 3% Heap Unclassified summary windows10-64-vm opt 43,692,487.64 -> 44,884,589.16 You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=7299 On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a treeherder page showing the jobs in a pushlog format. To learn more about the regressing test(s), please see: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/AWSY
:chutten, I see you authored the patch in bug 1335343, this appears to have caused a slight increase in memory for windows 10, could you confirm this is expected? I am not sure if there are things we could do to reduce this increase in memory.
Component: Untriaged → Telemetry
Product: Firefox → Toolkit
Each histogram now has to tell us what processes it is permitted to be recorded in. This requires a uint32_t per histogram (as many as 1556) per process (not sure how many processes that uses). This should be across all processes. There's nothing to be done for it, it's just a cost we now have to bear to make data reporting better. Do you need more information?
Flags: needinfo?(chutten) → needinfo?(jmaher)
Oh, that being said, we are refactoring how this influences storage in bug 1366294, so this will change a bit in the near future.
great to hear this isn't a surprise or not possible!
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.