Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

By γ (gamma)
Founder
I’m running an api endpoint, and it seems like I’ve hit some droplet limit of 510 or so concurrent connections. 32gig 4 cpu ubuntu 20.04, nginx is optimized. I do have ssl passthrough with a load balancer setup, but only running one droplet under the load balancer while I figure out why the droplet is getting so few connections. I’m running an api service, which will have many thousands of concurrent connections. I have a back end api service, proxy pass to :443. I’m looking a sysctl adjustments now, but that’s my last option to see what’s up with this limit… my droplet isn’t getting hardly any load during my load tests, if I was getting out of memory errors, I’d be happy, that would mean I’m pushing the server, but I think maybe there is an undisclosed DO rate limit on tcp connections, but there isn’t any documentation I’ve found to support that hypothesis. So I’m posting here to see if anyone has/had a similar situation. I like DO, used it for years. I’m just doing more than websites, and I think I may be trying to exceed the capability of DO… any help/insight would be helpful. thanks.
David Nusbaum
David Nusbaum
douser123
hss
digitalthinkingt
99a6f7638e10487f889daa3e4a233a
shivendrakushwah
adrilef
agenteAND
smmaamri