Been working on my own social platform, Y-Dude, and today I finally decided to see how much punishment the current backend can take. 😂

I ran a concurrent-user load test:

🟢 250 users — stable

🟢 500 users — stable, \~2.9s average

🟡 750 users — \~8.4s P90, 0 errors

🟡 1,000 users — \~10.6s P90, 0 errors / timeouts

RAM was around 66%, disk 18%, and the database itself wasn't really struggling. The bottleneck appears to be the backend/concurrency layer rather than the DB.

So apparently my little setup can handle 1,000 simultaneous users without falling over. 😂

Obviously, that's nowhere near saying the platform is ready for 100k concurrent users. But for an open beta, I'm pretty happy with the result.

Next step is probably not adding more features. I want to keep optimizing the existing system and make the backend properly scalable before worrying about huge numbers.

Y-Dude is a social platform built around local slang, sounds and regional culture — basically “Speak local. Connect global.”

Now I just need some actual humans to break it instead of my load test. 🤣

Would you trust this setup for an early beta, or would you improve the backend before opening it up?

I just stress-tested my social platform to 1,000 concurrent users