News for hackers. Stuff that matters.
Re:Why new Firefox 13 'load tabs on demand' is bad UX. by agumonkey on Tuesday June 05, 2012 @01:39PM (#4069734)
Resource prefetch would be good. I don't even know if it's possible for applications to throttle cpu/thread usage.
Re:Why new Firefox 13 'load tabs on demand' is bad UX. by illumen on Tuesday June 05, 2012 @01:43PM (#4069757)
Threads and processes can be given a lower priority.

Edit for @barrkel: you can also do more advanced resource shaping on some OSen. Like limiting the number of network connections per second, and limiting the bandwidth. There are also cpu throttling possibilities where you can make sure a process only runs max 10% of cpu. Or as you say, putting scheduling into the app is another possibility.

Re:Why new Firefox 13 'load tabs on demand' is bad UX. by barrkel on Tuesday June 05, 2012 @02:22PM (#4070004)
Lower priority does nothing to throttle activity unless there is a higher priority thread available to run; if the machine is otherwise idle, lowest priority threads will use 100% of CPU resources. If you want to avoid high CPU graphs, whirring fans from increased heat, etc., you need to make the thread or process sleep occasionally.

For a thread, that's best done with explicit coding; for a process that isn't sharing resources with other processes, you can get away with more invasive freezing from the outside.

Re:Why new Firefox 13 'load tabs on demand' is bad UX. by agumonkey on Tuesday June 05, 2012 @02:42PM (#4070142)
I guess it's possible to code a tiny arbiter that will wake 'background' thread every few ms.