Richard Schneeman

I'm not keen on this complexity living at this level. Others might disagree, but I think we have more than enough complexity in the current implementation to keep our hands...

> Returning 429 to the latter is not really an option; some federated implementations deal with timeouts better than they deal with 429s, If the requests are coming from inside...

Short: I was going to close the issue before I replied. I should have spelled out why, but I tend to write too much or too little. I think the...

> I believe the implementation as-is would not work properly Agreed, I left some notes in the issue about more thoughts. Thanks a ton for the PR. Even if it's...

> Should it be made clear that Puma only runs CI on the latest patch version of each Ruby minor version, and we recommend using it? Yes. I think that's...

For completeness: I just swapped the default branch name from `master` to `main`, you don't need to do anything for this PR. You'll need to update your local environment accordingly:...

I just swapped the default branch name from `master` to `main`, you don't need to do anything for this PR. You'll need to update your local environment accordingly: ``` $...

I think this wouldn't be due to the sleep worker calculations (since it's not in worker mode). Still, there are some other miscellaneous fixes, like that condition variable change in...

I'm able to reproduce the results. Here's numbers I'm seeing with various puma versions (locally) - with puma 6.6.1: 55,669 - with puma 7.0.0.pre1: 13,493 - with puma 7.0.2: 13,542...

A quick update. I modified the tech empower benchmarks to use a local puma folder ```diff --- a/frameworks/Ruby/rack/Gemfile +++ b/frameworks/Ruby/rack/Gemfile @@ -33,7 +33,7 @@ group :pitchfork, optional: true do end...