syzygy wrote:diep wrote:while gettickcount does give you milliseconds precision, it's very accurate milliseconds precision, which effectively is more accurate than linux microsecondsprecision in GetTimeOfDay; for the simple reason that windows kernel is in assembler and this is just moving the register to the user function, whereas the linux kernel is in C, so it's less accurate than GetTickCount, other than the millisecond resolution you get back versus microsecond resolution.
That "simple reason" doesn't make so much sense, does it?
Maybe you oversimplified it?
Nah i'll take the vision of the windows kernel team there, not so much whatever bla bla the msdn wrote 20 years ago
Haven't you read the recent AMD gpu documentation by the way?
Basically the currenth helpdesks lack so much technical information, yet make 100 rupees a month as a salary, that they even cut away diagrams and rewrite things to incomprehensable statements that basically no longer give clear information on how the GPU looks like.
I wonder how someone with just that recent documentation is gonna try to understand how the internals of a GPU work
It's the same thing at so many helpdesks now which write the technical documentation. Cheap labour replacing the insides. We shouldn't do as if that doesn't happen
It's difficult to compete with $1.11 an hour labour simply. Yet for them that's little as well, so the real experts they can't hire for that over there either. So they aren't there simply.
Add to that, usually they give support for hardware and software that they simply do not have themselves. Try to give support for a hardware component you have never ever seen in your life
I can give examples there that you wouldn't believe...
As for gettickcount, i can confirm with Diep that it's very accurate meassuring for Diep. I have a debug option to turn on all sorts of statistics under which measuring how long each core effectively has been searching.
One would GUESS doing that with gettickcount() doesn't give an accurate picture. Yet it does.
If you'd realize Diep also has an idle loop for a cpu, and that it isn't counting when a cpu is in there, then you start to get an impression slowly on how accurate this GetTickCount() works.
So i have 2 confirmations of it working very accurate, to the millisecond accurate