tstudio:
to answer original:
you cant tune windows either.
I mean, did you notice that?
I mean where is the registry entry?
Ive been waiting for these OSes to have something like this:
OS Features: Auto, CPU 1, CPU 2, PErcent slice
Disk features: Auto, Cpu1 , cpu2, percent slice
App features: Auto, Cpu1 , cpu2, percent slice
Ok so now you want SCSI disk on CPU1, 1000baseT on CPU2,
MPEG encoding on CPU1, here come 5000 TCP connections to CPU2 to Apache from the web (through the stack on CPU1).
Get the picture?
These OSes all schedule things dynamically because the kernel knows best whats afloat.
The scheduler says: I have resources, lets dole them out.
The apps, drivers, tasks, services, processes all say:
give me power.
who knows best how to slice and dice?
the kernel.
Ive played extensively with SQL 2000 on a 2 CPU P3-800 Dell.
Poweredge 1400SC.
The profiler and graphical query plans show parallel work
going on, especially where data is on two spindles.
The merge joins etc.
Now who makes the best kernel:
no doubt religious debate of course.
Novell allows code to run.
Cutler and Linus preempt code to prevent lockups.
Novel DEmands good coding.
MS/Linus dont care about wayward code.
But im getting off topic....
MS just put IIS in ring 0.
Whats next? Excel as a SYS driver?
(MS started to "throw all down to ring 0" in the NT days as they realized NT/2000/2003 is a dog without massive caching and more kernel time.
GDI used to be an application.
Now its a kernel driver.
Novell at least lets you set SOME SMP parameters.
MS has one: backrground, foreground. Services or Apps.
Not very granular.
But again, Novell programs for IT gurus.
MS programs for cashiers.
MS: "Only we know how to write and Run (your) code"
Novell: let the code run......if you mess up....we lock up
one favors speed
one favors.....something else
nuff said
flames?