| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | tourist | 3803 |
| 2 | jiangly | 3707 |
| 3 | Benq | 3627 |
| 4 | ecnerwala | 3584 |
| 5 | orzdevinwang | 3573 |
| 6 | Geothermal | 3569 |
| 6 | cnnfls_csy | 3569 |
| 8 | Radewoosh | 3542 |
| 9 | jqdai0815 | 3532 |
| 10 | gyh20 | 3447 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | maomao90 | 168 |
| 2 | awoo | 163 |
| 3 | adamant | 162 |
| 4 | maroonrk | 152 |
| 5 | nor | 151 |
| 5 | -is-this-fft- | 151 |
| 7 | atcoder_official | 147 |
| 7 | TheScrasse | 147 |
| 9 | Petr | 145 |
| 10 | pajenegod | 144 |
in codeforces judge it is (or at least it was) pretty common to get 999ms time on a problem with 1000ms time limit.
but I saw some submission getting 2500ms time on 2500ms a problem with 2500 time limit.
has the rules of codeforces changed so it doesn't consider it time limit exit or the judgement system of codeforces has changed so it can get 2500ms time and it couldn't before?
i think this is a rare moment for yours, just +1ms and game over.
Imagine getting +1ms , i would be so pissed.
CF has always been allowing just-in-time executions. It's just that the ones that actually exceeded the limit are shown as the exact limit, but they are not the same.
The reason why we can't see exact 1000ms AC submissions is because CF's time estimation depends on the system's clock cycle, and its precision is not very high. Due to this some time intervals just can't exist (or are much rarer than others). I think https://stackoverflow.com/questions/3744032/why-are-net-timers-limited-to-15-ms-resolution would explain.