System.nanoTime(): good or evil?

[oNyx]

>you realize that it's only a problem on multi-core cpus?

Heh. That would be nice. But there are a dozen different issues with QPC.

I got a single core and QPC is unusable (QPC leaping).

[fletchergames]

did you read the whole thread? you realize that it's only a problem on multi-core cpus? Sorry if you are talking about them, I got impression that you aren't.

When using System.nanoTime() on my computer with a single-core CPU, the game I wrote would suddenly pause for about half a second every once in a while (about once per level).  When using the millisecond timer instead, this problem stopped.

So System.nanoTime() has problems on single-core processors (or at least on mine) as well.  System.nanoTime() is evil.

[erikd]

I've talked with some other (non-java) developers about the issue, and all of them (okay, they were just 3 people ) use 1ms timing instead of QPC for exactly the same reasons.

Games published by our own members! Check 'em out!

[Kova]

damn Sun developers, why did they used damn QPC ... is there a RFE or bug report on this? It has to be.
I've heard LWJGL times is good, why don't they just use that, or whatever it's based on.

[erikd]

..I suppose because the RFE it was based on required high precision, and LWJGL's timer is just 1ms.
I'd rather see a currentTimeMillis implementation with 1ms precision on Windows.

[oNyx]

Somehow, I would like to see that. However, since TGT is something completely different (and may not work properly on some systems, too) a new method would be required if you don't want to create regressions.

The most logical name would be...
System.milliTime() (although... I would like msecTime() more )