Kernel 2.6 Real-Time Benchmarks
An anonymous reader writes "This whitepaper at LinuxDevices.com includes benchmarks comparing the real-time performance of the vers. 2.4 and 2.6 linux kernels, based on LynuxWorks' BlueCat Linux 5.0 beta. The graphs compare the results for average and worst-case measurements of both interrupt response and task switch performance for the two kernels, running on a 1GHz Pentium III under relatively heavy load. Check it out -- there's an enormous improvement. The article also includes a rundown of other features of the new kernel that seem likely to be welcomed by embedded developers."
The article (Yes, I RTFA.) talks about the responsivness of the new kernel, showing dramatic improvements in active and maximum latencies. Yet at the same time, there are people working very hard on a set of 'interactivity patches' and complaining of skipping when playing music on 2.6.
I haven't followed those discussions back to the beginning, so I don't know if they're gilding the lilly. But the intense work on interactive scheduling *now* scares me about like the late work on the VM did with the 2.4.0 release.
Just like the VM was the Achilles heel of 2.4 will interactive response, particularly playing music on a system under load, be the bane of 2.6?
The living have better things to do than to continue hating the dead.
May I re-ask the question I asked on Monday? And maybe throw in one of my responses for good measure? Again, not trolling - just looking for all the information I can amass.
Thanks.
i second that. I write software for the psychology dept at our univ, designed to do reaction time experiments. In basic priming experiments, we need accuracy up to at least 3 msec, preferably 1msec. For eye-movement detection I'd like even finer measurements, but under windows that's simply impossible.
accuracy up to 1msec is feasable by using a sufficiently fast machine (1GHz or more) with enough ram (512 at minimum) and VRAM (64min, more if you want speedy pics), removing network adapters & USB equipment and beefing the process priority up to max.
But even under those conditions, I occasionally lose a msec here or there. I wonder how OSX behaves under the same conditions...
When will I end this grieving ? When will my future begin ?
Assumeing you have one, this is a job for your computer science department. They have the people who know how to do this, and you can get plenty of under grads who will work cheap for expirence and their name on a paper.
A true CS department will also not be so windows focused, and help you fight the IS fools^h^h^h^h^hpeople who insist they know the best way to do your job.