Random_Bulshit_Submit's blog

By Random_Bulshit_Submit, history, 3 weeks ago, In English

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?

»
3 weeks ago, # |
  Vote: I like it -6 Vote: I do not like it

i think this is a rare moment for yours, just +1ms and game over.

»
3 weeks ago, # |
  Vote: I like it 0 Vote: I do not like it

Imagine getting +1ms , i would be so pissed.

  • »
    »
    17 hours ago, # ^ |
      Vote: I like it 0 Vote: I do not like it

    Yeah but then you wouldn't really know unless you test your code on the same hardware and tests

    • »
      »
      »
      16 hours ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      Oh yeah , but you would know after the contest , that would be 100 times worse.

      • »
        »
        »
        »
        15 hours ago, # ^ |
          Vote: I like it +1 Vote: I do not like it

        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?

        • »
          »
          »
          »
          »
          13 hours ago, # ^ |
            Vote: I like it 0 Vote: I do not like it

          No??? There is a Time section between Verdict and Memory.

          • »
            »
            »
            »
            »
            »
            11 hours ago, # ^ |
              Vote: I like it 0 Vote: I do not like it

            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.

            • »
              »
              »
              »
              »
              »
              »
              8 hours ago, # ^ |
                Vote: I like it 0 Vote: I do not like it

              Im acoustic.

              • »
                »
                »
                »
                »
                »
                »
                »
                7 hours ago, # ^ |
                  Vote: I like it 0 Vote: I do not like it

                LOL don't worry about it, happens to the best of us.

»
3 weeks ago, # |
Rev. 2   Vote: I like it +1 Vote: I do not like it

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.