At 22:14 6.11.2000 +0100, you wrote:
>Using currentTimeMillis() extensively has its drawbacks. First of all it is
>not very accurate, and can "skip" milliseconds so that two consecutive calls
>can give 10 ms differences.
Well, its only inaccurate on NT that can't seem to handle anything reliably
that takes <10ms to run. It has always worked fine on Linux (can get 1ms
accuracy).
You're right about cTM being expensive, which is why the metrics should be
configurable from the container factory so it can be skipped when you're
not analyzing your system. However, the tests I ran with the HelloWorld
test which I thought measured the time it takes on the "stack" didn't show
that big of a degrade to make it useless.
Of course, this can vary depending on the system being used. Mine is slow.
And if you have better suggestions on measuring time than cTM, I'm all ears.
-- Juha
