On 2015-08-17 7:21 PM, Kartikaya Gupta wrote:
FWIW one of the original driver behind Eideticker (tuning Fennec for checkerboarding during scrolling) will become relevant again in the next couple of months as we transition Fennec to using the C++ APZ code and off the old Java pan/zoom code. While it would be nice to have Eideticker around to give us data on performance characteristics during this transition, I'm not sure if it would be worth the effort to get it up and running again.
It wouldn't be an enormous amount of effort to keep it running (it's still going against m-c, as long as the device I'm using doesn't fall over, which happens depressingly often): I guess the question is whether the results it produced would really be relevant for you. As I said, the tests that we run for checkerboarding are pretty out of date at this point. Who really cares about a copy of CNN.com from mid 2012?
This is fixable, of course, but then the question becomes whether cycles would be better spent on Eideticker or something else. It's nice to have the video logs, etc. but at this point I'm feeling like synthetic benchmarks like Talos or Autophone offer better bang for the buck, especially now that they're hooked up to treeherder/perfherder and are thus useable via try, etc.
I know that tcheck is still running in automation (https://treeherder.mozilla.org/perf.html#/graphs?timerange=7776000&series=[mozilla-inbound,c233ba1133abbd544002dfbc29d9e63ced42a20e,1]), maybe we could just expand on or modify that?
Will _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
