On Tue, Mar 5, 2013 at 11:47 AM, Dave Mandelin <dmande...@gmail.com> wrote: > > It appears that there a few areas that are only covered by Talos for now, > though. I think in that category we have warm startup time via Ts, and basic > layout performance via Tp. I'm not sure about memory, because we do seem to > detect increases via Talos, but we also have AWSY, and I don't know whether > AWSY obviates Talos memory measurements or not.
Talos memory measurements aren't very good because it cycles through multiple sites in a single tab. So it sometimes catches start-up memory consumption regressions (Firefox Health Report was a recent case) but it doesn't get much beyond that. In comparison, AWSY cycles through 100 sites with 30 tabs open at once, which is a much better reflection of typical browsing. It also does multiple measurements -- start-up, after loading the tabs, after closing the tabs, etc. It's worth pointing out that AWSY is sort of built on top of Talos -- its 100 sites are taken from the Talos Tp5 set. The good thing about this page set is that they're stored entirely locally. The downside is that all the external stuff in the pages (e.g. Facebook "Like" buttons, Google Ad stuff, Twitter feeds) isn't present, so it's a not particularly realistic representation of those pages; in particular, the amount of JS present is much less than real pages have. (https://bugzilla.mozilla.org/show_bug.cgi?id=679940#c31 is an example of the effect of this in action.) Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
