| # | 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 | 161 |
| 4 | TheScrasse | 159 |
| 5 | nor | 158 |
| 6 | maroonrk | 156 |
| 7 | -is-this-fft- | 152 |
| 8 | SecondThread | 147 |
| 9 | orz | 146 |
| 10 | pajenegod | 145 |
System Test Case After Hacking Phase Long Queue Solution
After the hacking phase of Every Educational round/Div3 round, We all know that there is a long queue of submission and it takes a lot of time for testing.
Can't Codeforces silently test those submission slowly during hacking phase and store the judgements in the cache memory and then after hacking phase, run those submissions only on the new tests/hacking test. this will save a lot of time I guess...
What are your views on this design?
| Rev. | Lang. | By | When | Δ | Comment | |
|---|---|---|---|---|---|---|
| en3 |
|
rozerhacks | 2020-05-29 10:01:52 | 40 | Tiny change: 'is design?' -> 'is design?\n\n[user:MikeMirzayanov]\n\n' | |
| en2 |
|
rozerhacks | 2020-05-29 08:08:24 | 7 | Tiny change: 'ubmission during ha' -> 'ubmission slowly during ha' | |
| en1 |
|
rozerhacks | 2020-05-29 08:07:53 | 496 | Initial revision (published) |
