>How easy is it to identify CPU-sensitive tests? Easy for some (most but not all media tests). Almost all getUserMedia/PeerConnection tests. ICE/STUN/TURN tests.
Not that easy for some. And some may be only indirectly sensitive - timeouts in delay-the-rendering code, TCP/DNS/SPDY timers, etc, etc. Anything that touches a timer even indirectly *could* be. So, large sections *could* be. I suppose we could include code checking for MainThread starvation as a partial check though that won't catch everything. >I think the most practical solution (at least in the near term) is to find >that set of tests, and run only that set on a faster VM, or on real >hardware (like our ix slaves). That was an option I mentioned. It's not fun and will be a continual "is this orange CPU sensitive?" as they pop up, but it certainly can be done. And it may be simpler than better solutions. -- Randell Jesup, Mozilla Corp remove "news" for personal email _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
