Depending upon where exactly your 2.x seconds measurement for 10000 iterations landed, this makes perfect sense.
> Moreover one second are 1000 ms, not 1024.
This is an old trick -- dividing an integer by 1000 is a lot more work than dividing by 1024. If this is only done once it's a bit silly but if it is done in a tight loop it can have surprising impact on the performance.
> 60000 I get 18 seconds and 10000 is 2 seconds.
60000 / 10000 == 6.
2.1 * 6 == 12.6
2.2 * 6 == 13.2
..
2.9 * 6 == 17.4
Depending upon where exactly your 2.x seconds measurement for 10000 iterations landed, this makes perfect sense.
> Moreover one second are 1000 ms, not 1024.
This is an old trick -- dividing an integer by 1000 is a lot more work than dividing by 1024. If this is only done once it's a bit silly but if it is done in a tight loop it can have surprising impact on the performance.
Thanks