Nginx proxy is not working about graphql-benchmarks HOT 3 CLOSED

The PR only disabled the access logs on nginx, which just increased it's throughput. This increase improved the performance of all the servers including caliban.

The connection errors happen because caliban doesn't close the connections immediately after the test is over, which results in residual port usage sometimes. I think if you add a finalizer using ZIO where the client is also closed, it would fix the issue.

from graphql-benchmarks.

@tusharmath The reproducer I provided was with using tailcall, althought it's the same across all server implementations

from graphql-benchmarks.

Just to clarify: This is not an issue with the server(s). The call to the proxy is falling, which in turn causes the servers to (correctly) return an error instead of the expected response.

from graphql-benchmarks.