Anyone find these numbers familiar?
Hint
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
2 | maomao90 | 163 |
4 | atcoder_official | 161 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | nor | 153 |
9 | Dominater069 | 153 |
Anyone find these numbers familiar?
15 ms, 31 ms, 46 ms
Why do these numbers appear so often as the runtime of submissions?
Название |
---|
Does it mean that I'm likely getting tl if my code run for 998ms due to this derivation?
Maybe it is a=15.(something) and these are just multiples of a... for very small programs the time is dependent on constant factors?
Maybe the judges of Codeforces can't get the accurate executing time.
...or just solve the problem of judging stress.
$$$15=15 \times 1+0$$$
$$$31=15 \times 2 +1$$$
$$$46=15 \times 3+1$$$
$$$62= 15 \times 4+2$$$
I checked my submissions. Common running times include "0, 15, 31, 46, 62, 77, 93, 108...".
The adjancent-difference of them are +15, +16, +15, +16, +15, +16, +15...
But there are 30ms, 61ms, 78ms in my submissions.
So it seems that the submission time tends to be $$$T = \lfloor ak\rfloor (k \in N+), a\approx 15.45$$$ milliseconds. I guess it's because the period of the time counter.
As python user I can't relate