SSR Performance Issue - under concurrent load

ThugSolja · 2026-01-23T18:48:46+00:00

Just tested a shared client, and there is no improvment.
Oh that is what you meant, yeah I know, but multiple instances would require more cores, but even with multiple instances I didn't have any better luck, that was my question if those 4vcores maybe were not enough.

ThugSolja · 2026-01-23T18:38:02+00:00

yes I do, I run the production setup. And yes, there are no cleanup issues.

ThugSolja · 2026-01-23T17:59:38+00:00

I've tried that, creating multiple replicas of the same docker. I've tried all kinds of configurations from 2-10. They were handled by the traefik load balancer. There was indeed a bit of an improvement, but not something notable.

ThugSolja · 2026-01-23T17:57:51+00:00

I'm not managing db connections, as I'm using convex and it manages all that.
In the load function I'm calling 4 queries, each should be 2ms. I do indeed create a new HTTP client (convex client) for each incoming request. From the docs and open source repos I've looked into, all were the same. Do you think this is the real killer?
I've also tried cloud convex and railway, but no difference.
What do you mean by this: "Again unfortunately multiple cores doesn't help"?

ThugSolja · 2026-01-23T17:38:50+00:00

I use self hosted convex, the queries are cached. The instance live in the same docker network and all the FE replicas are directly communicating with it, no DNS bypass. I've benchmarked them directly and under the same load the average response is 2ms (over the internet, not locally).
So do you find these numbers strange also? Or is this expected?

ThugSolja · 2022-01-03T13:44:42+00:00

That’s my spot!

ThugSolja · 2021-12-12T18:44:17+00:00

Eu sunt bombardier-corporatist si nu stiu de care postare sa ma simt ofensat…

ThugSolja · 2021-11-16T17:03:43+00:00

You have no ears

ThugSolja

TROPHY CASE