Suggest to change the timeout: instead of the count: when timeout is reached
Created by: mike-r-mclaughlin
Feedback
In this example, the server appears to have timed out. It doesn't matter how large of a number that is provided to count:, it will still always return ~75 results. And, it always seems to take roughly 60s (the default). Perhaps the suggestion should be to change the default timeout: parameter instead?