Answer by PM on gitter.

Quite many users experience timeouts because they do not account correctly for edge cases. I'd suggest adding fixed test(s) which would show users the tricky parts and would hopefully reduce amount of invalid issues, complaints, and support activities on this kata.

The task in Java seems to work well, and I believe you are handling some edge case incorrectly.

Check if you account for this part of the description:

Three conditions must be met for a valid experiment:

• Float parameter "h" in meters must be greater than 0
• Float parameter "bounce" must be greater than 0 and less than 1
• Float parameter "window" must be less than h.

If all three conditions above are fulfilled, return a positive integer, otherwise return -1.

My solution always quickly then best solution (in miliseconds), however my result always timeout
My language - JAVA.
it's very bed task ((;

It's very easy task !:)