this post was submitted on 04 Jan 2024
111 points (95.9% liked)
Programming
17423 readers
73 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
1,200,000 / 30 days / 24 hours / 60 minutes / 60 seconds is 0.46 requests per second.
That is crazy low and is nothing to shout about. I notice people like to this in months to inflate the number to looks bigger. But calculating it down to RPS puts it to a perspective.
PHP 8.0 is no longer supported so I hope they update the "really, really old technology" to at least PHP 8.1 today.
Either way that VPS will cost 10-20$ depending on CPU form a good provider. You can't get that cheap with a bunch of AWS services for that number of requests.
Also, if they were using an hyped tech stack (nodejs or wtv) they wouldn't be able to handle the request spikes like they do. 0.46 requests per second means nothing because I'm sure they've hours of full inactivity and others serving 10 requests / second that would totally obliterate 2GB of ram if done on nodejs and a Mysql DB.
$10-20 is what that VPS costs at a cloud provider. You could also dockerize and use a container service like GCP Cloud Run combined with cloud storage within that budget.
I'm not a big node guy, but I also kind of doubt nodejs would fail to handle 10RPS on 2gb of memory. I guess it all depends on what the requests are doing.