low latency versus sched O(1)

[=?ISO-8859-2?Q?Martin_Ma=E8ok?=]

I have tested Andrew Morton's low latency patch versus Ingo's sched
O(1) patch a bit:

"O1" is 2.4.18-pre2 + sched-O1-2.4.17-G1

"LL" is 2.4.18-pre3 + 2.4.17-low-latency + riel's 2.4.3ac4-largenice

(Red Hat 7.2 Linux, UP Athlon CPU 850MHz)

Comparison:

Tuxracer:
 - reports same framerate on both when no other load is on the
   machine and the game is smooth in both cases.

Tuxracer + kernel compilation (both nice 0):
 LL: the game skips a lot, ugly :(
 O1: the game skips much less than LL, playable

Tuxracer + kernel compilation with nice +19:
 LL: no skipping, almost same as without kernel compilation
 O1: skips a little less then with kernel compilation (nice 0)
     but skips much more than LL in this case.

Xmms/Jess visual plugin:
 - same framerate when no load
 (LL: maybe a little bit larger (+10%) framerate than O1)

Xmms/Jess + kernel compilation:
 LL: almost doesn't work, very bad :(
 O1: lower framerate (1/3), skips a little, but works

Xmms/Jess + kernel (nice +19):
 LL: almost exactly same as LL without kernel compilation!
 O1: framerate somewhere between.. skips ocassionaly

Conclusion:
This is not a real test nor real benchmark, only a little stupid luser
test, but it can show that LL is much better in interactivity and
smoothness but you HAVE to setup priorities (nice levels) of tasks by
hand (explicitely). When you don't setup priorities explicitely than
sched O1 makes the job for you but don't achieve same
interactivity/smoothness performance as LL.

So I suggest a combination of some conservative LL + O(1) scheduler
will make linux desktop kicking ass! :)

-- 
         Martin Mačok                 http://underground.cz/
   [e-mail]        http://Xtrmntr.org/ORBman/