Can some explain why Windows timing is so bad?

[Stiganator]

Why is it that Linux and OS X can do it correctly, but Windows cannot?

I've run into it with programs too.

Matlab filter on Windows : 4.83 sec (really 44 seconds)

Matlab filter on OS X : 44 secs (really 44 secs)

 

[Crusty]

It's just an estimate, there's no way to tell what the computer is going to be doing or what the user will ask the computer to do in the near future. Sure there might be a different way to guess, but for the most part guessing when something will be done is usually based on the current rate that the job is being done.

What you might be seeing is that a different OS assigns a different priority to certain tasks. If a task has a high priority then the guesswork should be more accurate due to less time yielded to other tasks/processes and worse if it has a lower priority.

 

[seemingly random]

I've found that xp did it much more accurately than vista.

*pot stirred, getting popcorn*

 

[oog]

there's a pretty good explanation here: http://blogs.technet.com/markr...008/02/04/2826167.aspx

 

[Madwand1]

Originally posted by: oog
there's a pretty good explanation here: http://blogs.technet.com/markr...008/02/04/2826167.aspx

:thumbsup: