April 30, 2009
4:04 a.m.
Where do I reduce that priority? -cam On Apr 29, 2009, at 11:40 PM, John M McIntosh wrote:
But let's consider what's NEW here is the 'input events fetching process' is now running at 2x the speed of the older UI process and consuming 10-30% of the cpu? I'm not sure why before it was acceptable to look every 1/50 second, but now it has to be every 1/100 of a second.
But it's interesting that it''s running at priority 60, which means it's sucking CPU away from the weak array finalization process.