On Monday 17 March 2008 20:28, Peter Zijlstra wrote:> Nick,>> We do grow the period as the load increases, and this keeps the slice> constant - although it might not be big enough for your taste (but its> tunable)>> Short running tasks will indeed be very likely to be run quickly after> wakeup because wakeup's are placed left in the tree. (and when using> sleeper fairness, can get up to a whole slice bonus).>> Interactivity is all about generating a scheduling pattern that is easy> on the human brain - that means predictable and preferably with lags <> 40ms - as long as the interval is predictable the human brain will patch> up a lot, once it becomes erratic all is out the window. (human> perception of lags is in the 10ms range, but up to 40ms seems to do> acceptable patch up as long as its predictable).>> Due to current desktop bloat, its important cpu bound tasks are treated> well too. Take for instance scrolling firefox - that utterly consumes> the fastest cpus, still people expect a smooth experience. By ensuring> the scheduler behaviour degrades in a predicatable fashion, and trying> to keep the latency to a sane level.

Yeah, and firefox scrolling is in the class of workloads where theyadaptively reduce CPU consumption as they get less quota (ie. becausethey just start skipping).

Still, for desktop workloads you shouldn't have to deal with lots ofCPU hog processes on the runqueue, so I don't see why this is needed?

I don't mind having the timeslice smallish, but it shouldn't bereduced as load increases.

> The thing that seems to trip up this psql thing is the strict> requirement to always run the leftmost task. If all tasks have very> short runnable periods, we start interleaving between all contending> tasks. The way we're looking to solve this by weakening this leftmost> requirement so that a server/client pair can ping-pong for a while, then> switch to another pair which gets to ping-pong for a while.>> This alternating pattern as opposed to the interleaving pattern is much> more friendly to the cache. And we should do it in such a manner that we> still ensure fairness and predictablilty and such.>> The latest sched code contains a few patches in this direction> (.25-rc6), and they seem to have the desired effect on 1 socket single> and dual core and 8 socket single core and dual core. On quad core we> seem to have some load balance problems that destroy the workload in> other interresting ways - looking into that now.

Yeah, thanks for looking at that. Wow, scheduler patches sure makeit upstream a lot quicker than when I used to work on the damn thing ;)

I did a quick run and it seems like the postgresql overload problem isfar better if not solved now on my 2x quad core. Haven't had time toget some reportable results, but I hope to.