Forums Register Login

Strange results for time taken

+Pie Number of slices to send: Send
Hi, for my rubiks cube, I timed the average time to do a repaint for each 'animated frame' of a twist of the cube.

Strangely, this starts off at about 16ms, then after several twists goes down to 12ms.
I can't see why this happens, possibly an impossible question to solve without experimenting with code, but is there any obvious reason for this?

Thanks for any help.
+Pie Number of slices to send: Send
- inaccuracy of the clock?

- optimizations done by the hot spot engine?
+Pie Number of slices to send: Send
I have had the same phenomonon with AffineTransforms, which run faster the second time they are executed. Probably JIT (="just in time") compilation; when the HotSpot machine recompiles the repeatedly-used code, it runs faster.
+Pie Number of slices to send: Send
Also, the first time through it may still be loading some classes. This is pretty much normal behavior for Java programs - the Just in Time compiler makes things faster as they run more.
+Pie Number of slices to send: Send
I thought it still maybe doing some other work, but if I leave it for a minute after everything is loaded and ready to use, it still starts at 16ms, not a big deal.

I rather know that it isn't a fault with the code, and that its just one of those things.
brevity is the soul of wit - shakepeare. Tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 838 times.
Similar Threads
its right ??
Gui animation
Rubik's Cube Hell
Impressive Rubik's cube solver
Hot cubes
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 08:42:13.