> One case where timer-based scheduling is needed is when implementing a web browser. The JavaScript standard has a function called setTimeout which asks the browser to call a JavaScript function some number of milliseconds later. Chromium uses timers (mostly WaitForSingleObject with timeouts rather than Sleep) to implement this and other functionality. This often requires raising the timer interrupt frequency.
Why does it require that? Timeouts should normally be on the order of minutes. Why does Chrome need timer interrupts to happen many times per second?
This isn't the browser's network timeouts, this is the JavaScript function setTimeout() which can be used in scripts and which, as mentioned, takes an argument in milliseconds. Chrome needs to be able to support whatever setTimeout() call a website might make, and those are rarely going to be minutes long; setTimeout() is just used for "call this function after a specified amount of time". The fact that the word "timeout" is used in the name does not mean that it has any relation to network timeouts!
Why does it require that? Timeouts should normally be on the order of minutes. Why does Chrome need timer interrupts to happen many times per second?