Hello, I know we already have a few tests like this in the ReactOS tree but I have not had time to look at all of them or dig in to this at all.
I am forwarding part of a message from Jeremy White along with some tests of timers and schedualing in case anyone wants to compare Windows and ReactOS. We ran in to quite a few issues under CrossOver with Office applications and were able to work around them. Even applications such as Internet Explorer are affected. See recent hacky patches on wine-devel for winmm timer resolution. Anyway here is a bit of his notes and the collection of tests if anyone is interested.
Thanks Steven
".....Spinning threads get all the cpu they can chew; being in a foreground Window gives a pretty high bias, but otherwise things seem to be evenly spread. Aric did a test program which showed how SetThreadPriority biases things; it tends to be that only priorities -2 through 2,and 15, have any meaning. Further, if threads yield, then only thetop priority threads get any time. If all threads 'work', then there is a stair step effect where high priority threads get 'more', but don't necessarily get it all."
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
-
Steven Edwards