Gerhard Lazu

I'm still scrolling.

There we go.

It's super helpful.

I have confirms.

I've confirmed that the requests have been hanging.

You are getting the hangs this afternoon as well.

This was only three weeks ago.

So this has been going on for a while.

I dug deeper and I found the problem.

The problem was that in the fly config, we had the concurrency set to connections, not requests.

So it's possible to configure an application.

Again, you're configuring the fly proxy that sits in front of the application to limit how much traffic hits your application.

So requests, how many requests per second should the fly proxy forward to your application before it stops?

Because you don't want it to get overloaded.

So before it starts throttling, it starts slowing clients down.

And then when you start seeing fly edge errors.

connections you would use for something that has long-running connections, like a database, for example.

In our case, it's not a database, right?

It's an HTTP application.

So requests would have been the right concurrency.