# MGAME timeout

Can you please explain why my solution timed out for the second subtask? I used the same method described in the editorial:

https://www.codechef.com/viewsolution/22454513

I even submitted a DP solution with precalculated values:

https://www.codechef.com/viewsolution/22467759

This was a contest solution, it affects my score.

Edit:

I have tested I/O speed on the Enormous Input Test problem:

https://www.codechef.com/viewsolution/22491210

https://www.codechef.com/viewsolution/22491207

Both of them were accepted, the Console.WriteLine(count) version is little bit faster. How was I supposed to know my output is not fast enough?

Did you try to use BufferedReader?

Apologies for the language mix-up.

The issue is definitely with the I/O speed.

``````
Console.WriteLine(count);

``````

to

``````
Console.WriteLine("{0}", count);

``````

then you get an AC.

Also, printing each answer one by one is not a good idea for this problem, unfortunately. If T = 10^6, your code prints the answer 10^6 times, which may lead to TLE. I also had this issue and fixed it by collecting them in StringBuilder. See here: https://www.codechef.com/viewsolution/22199707
It somehow works in 1.65 sec. By the way, I/O speed is another concern as well.

plz anyone explain the logic i cannot understand editorial

plz anyone explain the logic i cannot understand editorial

It’s C#, not Java. I’m using the standard Console.ReadLine() as always.

Thanks a lot! I should’ve tested my I/O speed. It’s really annoying to lose points because of that.

Once the input/output size reaches 10^5, the I/O should always be a concern, and it may take non-trivial amount of time just to read the problem data and write the answers. It’s just one thing to keep in mind always.

I can’t view your solution for some reason, but yes, it makes sense to output like that. But it’s not necessary, if you just want to gain 100 points.

Already fixed the link. Yeah, I understand that. I got this issue in some long contest before and it is so annoying. Using Buffered Reader and do not print too often are always the best options.

You need to understand how modulo arithmetic works. Counting the possibilities is just a matter of combinatorics.