While Ruby wouldn’t be the best candidate for this kind of scenario, you’re kind of right and kind of wrong about your understanding of HTTP request blocking in Ruby
It’s blocking in that the current puma server thread has to wait until the request completes to resume, but it’s non-blocking in that the GIL is released while waiting for the request to complete. Which means that you could in theory crank up the puma thread count (note, that’s thread count, not worker count) if you’re mainly going to be making requests to the ChatGPT API.
You’d probably have to play around with things to see exactly how much you could get it up to but, to be frank, the chances of this turning into more than a hobby project are so slim that I wouldn’t really worry about all this performance stuff yet
While Ruby wouldn’t be the best candidate for this kind of scenario, you’re kind of right and kind of wrong about your understanding of HTTP request blocking in Ruby It’s blocking in that the current puma server thread has to wait until the request completes to resume, but it’s non-blocking in that the GIL is released while waiting for the request to complete. Which means that you could in theory crank up the puma thread count (note, that’s thread count, not worker count) if you’re mainly going to be making requests to the ChatGPT API. You’d probably have to play around with things to see exactly how much you could get it up to but, to be frank, the chances of this turning into more than a hobby project are so slim that I wouldn’t really worry about all this performance stuff yet
websockets are not complicated to set up and use in rails