4 ms·
There’s nothing in that thread that supports the assertion that this is taking ‘half a core’. The Finder sample shows it taking less than 10% of the wall-clock
by jrmg 6y ago
There’s nothing in that thread that supports the assertion that this is taking ‘half a core’.
The Finder sample shows it taking less than 10% of the wall-clock time of one (mostly idle) thread, and it doesn’t seem likely that WindowServer is spending another 40%+ of a core in response.
- saagarjha 6y agoThe thread focuses on the problematic code, not the performance impact it has. The second (collapsed) __CFRunLoopRun in the sample screenshot contains all the resultant drawing happening in-process, with which Finder used about 20% of the CPU. WindowServer was using about ~25% to keep up.