Stress-test backend

When I ran a batch process to execute a lot of backend requests concurrently, I got a 500 error. The workaround was I had to get rid of or slow down the concurrency.

I'd strongly suggest writing a simple tool that stress-tests the backend and that it should be run before going live

Here's some reference code, fwiw: https://github.com/ji-devs/ji-cloud/tree/sandbox/build-utils/legacy-player/transcode/src/create_jig

(this was written as just a one-off tool, i.e. doesn't handle errors elegantly and I sometimes adapted it with comments instead of real config options, just a reference for passing a reqwest client down to a bunch of async fns and having a max pool active at a time.)

Note that @mehcode said:

this [500] error means that the "max connections" param in the app doesn't match the max connections of your DB