Блог пользователя YocyCraft

Автор YocyCraft, история, 23 месяца назад, По-английски

I've just posted a topic complaining about slow judge, and it received 4 downvotes in just 5 minutes, so I have no choice but to delete it. So could someone tell me is it normal that a submission need to wating for over 10 minutes to be judged?

Update: Now my new submission 191736305 has got AC, but it also has waited for 6 minutes.

Update; Encounter a problem on CF ---> post a blog for asking for it ---> get downvoted by unknown reason ---> be forced to delete the blog to save contribution ---> encounter more problems. How can this vicious cycle be stopped? The greatest disadvantage of CF downvoting system: I will never know the reason I being downvoted.

Update: If you're getting annoyed by this blog, please comment something like "asking for system technical issue is not welcomed on codeforces" instead downvote.

  • Проголосовать: нравится
  • +46
  • Проголосовать: не нравится

»
23 месяца назад, # |
  Проголосовать: нравится 0 Проголосовать: не нравится

I'm not kidding, my submission 191734655 was sent on 19:13:00 and judged on 19:24:26.

»
23 месяца назад, # |
  Проголосовать: нравится 0 Проголосовать: не нравится

No downvote please. I post this topic just for asking for answer.

»
23 месяца назад, # |
  Проголосовать: нравится 0 Проголосовать: не нравится

Auto comment: topic has been updated by YocyCraft (previous revision, new revision, compare).

»
23 месяца назад, # |
  Проголосовать: нравится 0 Проголосовать: не нравится

i don't think it's a common thing for the queue to freeze like that :/, last time it happens to me was a few month ago

»
23 месяца назад, # |
  Проголосовать: нравится +3 Проголосовать: не нравится

It could be because of IZHO

»
23 месяца назад, # |
  Проголосовать: нравится +44 Проголосовать: не нравится

Just 10 minutes? I remember playing a virtual ICPC contest in the evening and getting my submissions testing only on the next day (thankfully, they all got accepted).

On a serious note: sometimes the system is overloaded due to testing of some ongoing event. Usually it happens during system testing after the rounds, and in that case it's easy to see what caused this. Maybe there's some hidden event with system testing going right now, maybe staff is analyzing submissions to remove cheaters and/or rejudge with added hacks. Usually it's a good idea to check the status of the problemset: if you see five pages of submissions in queue, this means that it's not the issue with your submission, it's just high load on the system.

»
23 месяца назад, # |
  Проголосовать: нравится +9 Проголосовать: не нравится

Once I did training contest and a little intersected with ongoing contest at last few minutes. My last solution was tested after an hour. However, during that contest there was no noticeable queue. So the system just strongly prioritises ongoing contests.