The last contest's Codeforces Round 590 (Div. 3) was very slow; every submit, was in queuing about 10 minutes. I've lost a lot of time.
Please fix these problems :)
# | User | Rating |
---|---|---|
1 | ecnerwala | 3649 |
2 | Benq | 3581 |
3 | orzdevinwang | 3570 |
4 | Geothermal | 3569 |
4 | cnnfls_csy | 3569 |
6 | tourist | 3565 |
7 | maroonrk | 3531 |
8 | Radewoosh | 3521 |
9 | Um_nik | 3482 |
10 | jiangly | 3468 |
# | User | Contrib. |
---|---|---|
1 | maomao90 | 174 |
2 | awoo | 164 |
3 | adamant | 162 |
4 | TheScrasse | 159 |
5 | nor | 158 |
6 | maroonrk | 156 |
7 | -is-this-fft- | 151 |
8 | SecondThread | 147 |
9 | orz | 146 |
10 | pajenegod | 145 |
The last contest's Codeforces Round 590 (Div. 3) was very slow; every submit, was in queuing about 10 minutes. I've lost a lot of time.
Please fix these problems :)
Name |
---|
and they added only 15 minutes to the time of the contest but the queue really affected someones more than 15 minutes .
Yes , this is an important problem
It has been going on like from last 2 or 3 contests. Hope to see this issue resolved in the next contest.
there's a huge amount of participants who's rating is > 1600. I mean... what's the point to participate on div3 contest for some red or yellow coder? Soooo, the solution is to ban everyone to participate who's reting more than 1600, I assume.
I got an even better idea, just ban a random 50% of CodeForces users.
Mike should not play pubg on it while solution is judging.