Threebow

Hi all, It seems that the more recent connection timeouts were being caused by our database setup and app architecture. The changes we made that have shown us significant improvement...

> Do you think there is anything concrete we should or could look into? Nothing particularly relevant to the initial scope of this issue, unless you think `BEGIN` and `SELECT...

We ran the exact same test in Java to confirm that the issue was not with our GRPC server. Here is the result: ``` > Task :Main.main() Starting test... Reached...

> [Our own benchmark](https://grafana-dot-grpc-testing.appspot.com/) shows significantly better performance than you are seeing there. Thank you for your insights and the reference to your benchmark. It's perplexing, indeed, that we're observing...

I conducted additional tests on both Java and Node, focusing on the "average delta" for each event received. The "delta" is the difference between when the payload was generated (as...

In a final (for now) test, which included tracking the peak delta (the longest single delay recorded), it became evident that Java didn't lag at all on any single request,...

Here's something interesting. I created a sort of "frankenstein solution". I set up the Java RPC consumer used in my tests to send an HTTP request to my Node server...

Thank you for your reply and the valuable information provided. Could this optimization be applied within our own codebase using this module, or would it require implementation on your end?

Okay, thank you for the update. We'll look for other solutions for now and keep an eye on future developments. I'd offer to help with a PR, but BDP-based dynamic...