Laurent Demailly
Laurent Demailly
While periodic export for long run is useful, I don't think it is related to: > we encounted a problem. Testing short connection though loadbalancer for 120s， with some connection...
I would try to understand why you are getting timeouts and why that impacts your expected QPS? Periodically reporting would not change the math; the qps is how many requests...
increase the -c if you have a few bad requests blocking the other ones. or figure out why that's happening? but either it's unrelated to this specific issue. thanks.
> The timeout bugs, we will try to figure out. If there is a periodically report, we can find the bug effectively. I agree! in the meantime remember, you can...
we'll reuse what @PiotrSikora finds in https://github.com/istio/istio/issues/3987 ! (though ideas/suggestions still welcome)
ditto for max-echo-delay
not that easy though to keep the feature (dynamic changing flag for these... would need some sort of callback) or move these handlers to a sub package (or the library...
You can test any grpc server using the standard health endpoint (as opposed to the custom fortio grpc ping endpoint) but yes at this point you can't test "any" grpc...
we should maybe also use the warmup to do (optional) automatic histogram bucket calculation (offset and resolution)
https://docs.github.com/en/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions