| # | User | Rating |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | Kevin114514 | 3659 |
| 3 | jiangly | 3640 |
| 4 | turmax | 3450 |
| 5 | tourist | 3382 |
| 6 | strapple | 3360 |
| 7 | Um_nik | 3354 |
| 8 | squareOf105 | 3348 |
| 9 | maroonrk | 3312 |
| 10 | idontwannadothis…e | 3191 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 155 |
| 2 | nik_exists | 151 |
| 3 | maspy | 149 |
| 4 | AmShZ | 145 |
| 5 | Um_nik | 143 |
| 6 | Errichto | 139 |
| 7 | BledDest | 136 |
| 8 | adamant | 134 |
| 9 | maroonrk | 132 |
| 10 | cry | 130 |
| Name |
|---|



Try fast cin, cout.
Thank you I got AC using fast i/o. Can you tell me why this (std::ios::sync_with_stdio(false);) speeds up input/output also when should we use fast i/o. ( I mean what is the maximum order of data read or written using cin/cout without fast cin/cout).
http://www.cplusplus.com/reference/ios/ios_base/sync_with_stdio/
in MinGW build used by codeforces printf/scanf is much faster than cin/cout even if you'll add sync_with_stdio etc. Tried printing 106 integers in custom test:
cout— 514 mscoutwithsync_with_stdio(false)— 467 msprintf— 202 ms