Confirmed users
699
edits
Gecko:NewPerfHarness: Difference between revisions
Jump to navigation
Jump to search
→Android (top priority)
| Line 68: | Line 68: | ||
* Using USB interface instead of WNIC (though adb can apparently instead use WNIC) | * Using USB interface instead of WNIC (though adb can apparently instead use WNIC) | ||
* adb-client competes for resources with other programs on device | * adb-client competes for resources with other programs on device | ||
* | * For a 800x480 phone (galaxy s), a 60fps screen capture would require 5.76MB/s. Max effective USB 2.0 bandwidth seems to be in the range of 40MB/s. The transfer can be optimized to not send successive duplicate runs of pixels at the cost of metadata and comparisons. A simple (non-optimal) row deduplication scheme bumps transfer requirement up to 5.7672MB in the worst case (all new rows every time). It's unclear how much the data transfer alone would disturb the device. It would likely significantly impact adb-over-USB if it's also proxying tcp for tests, but tests could use the idle WNIC instead of adb. The built-in screencap utilties are totally unoptimized and are not designed to be fast (or sync to vblank). We would need to write this screenvid prog from scratch (and it would need root on the device). Strain on CPU/memory bus/GPU(if any) is also unclear, although it's relatively easy to write an optimal implementation and measure. | ||
* Unknown latency, unknown cost of dispatching phony UI events | |||
* Requires a quiet host system, a la "Network" section | * Requires a quiet host system, a la "Network" section | ||
* Adb is flaky on windows machines | * Adb is flaky on windows machines | ||