| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | tourist | 4009 |
| 2 | jiangly | 3773 |
| 3 | Radewoosh | 3646 |
| 4 | ecnerwala | 3624 |
| 5 | jqdai0815 | 3620 |
| 5 | Benq | 3620 |
| 7 | orzdevinwang | 3612 |
| 8 | Geothermal | 3569 |
| 8 | cnnfls_csy | 3569 |
| 10 | Um_nik | 3396 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | Um_nik | 164 |
| 2 | cry | 160 |
| 2 | maomao90 | 160 |
| 4 | -is-this-fft- | 159 |
| 5 | atcoder_official | 158 |
| 5 | awoo | 158 |
| 7 | adamant | 155 |
| 8 | nor | 154 |
| 9 | maroonrk | 152 |
| 10 | Dominater069 | 149 |
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.
Yeah but then you wouldn't really know unless you test your code on the same hardware and tests
Oh yeah , but you would know after the contest , that would be 100 times worse.
How so? If you tried to use the codeforces judge it'd only tell you that you got a TLE, not the exact time your code took, correct?
No??? There is a Time section between Verdict and Memory.
Yes but when your code gets a TLE verdict and for example the limit for that specific problem is 2500ms it'd just say "2500ms" on your Time section, not 2612ms or something like that.
Im acoustic.
LOL don't worry about it, happens to the best of us.
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.