----- Original Message ----- > 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.
Another problem with the Talos memory tests, in comparison to AWSY, is that Talos opens and closes pages very rapidly, while AWSY proceeds at a more stately pace. This is very important for a memory test, because most of our GC and CC heuristics are time based. The drawback of this is that each test takes hours to run, though it is mostly just sitting around, so many test runs can be done at once on the same machine. > > 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 > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
