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 | tourist | 3985 |
2 | jiangly | 3814 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3517 |
7 | Radewoosh | 3410 |
8 | hos.lyric | 3399 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
# | User | Contrib. |
---|---|---|
1 | cry | 169 |
2 | maomao90 | 162 |
2 | Um_nik | 162 |
4 | atcoder_official | 160 |
5 | djm03178 | 158 |
6 | -is-this-fft- | 157 |
7 | adamant | 155 |
8 | Dominater069 | 154 |
8 | awoo | 154 |
10 | luogu_official | 151 |
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.