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 | jiangly | 3976 |
2 | tourist | 3815 |
3 | jqdai0815 | 3682 |
4 | ksun48 | 3614 |
5 | orzdevinwang | 3526 |
6 | ecnerwala | 3514 |
7 | Benq | 3482 |
8 | hos.lyric | 3382 |
9 | gamegame | 3374 |
10 | heuristica | 3357 |
# | User | Contrib. |
---|---|---|
1 | cry | 169 |
2 | -is-this-fft- | 165 |
3 | Um_nik | 161 |
3 | atcoder_official | 161 |
5 | djm03178 | 157 |
6 | Dominater069 | 156 |
7 | adamant | 154 |
8 | luogu_official | 152 |
9 | awoo | 151 |
10 | TheScrasse | 147 |
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.