Earlier quoted context omitted.
The top 5 web app programming languages by market share are PHP, Java, JS, Lua and Ruby.
...said a stranger on the internet without any sources to back up this claim.
Reining in the thundering herd: Getting to 80% CPU utilization with Django
21–30 of 139 posts
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#22Kinda funny they decided paying a ton of money to aws was ok but paying for nginx plus was not
And on top of that Nginx Plus is also expensive as hell.
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#23If it is just a backend, why not port it over to one of the myriad of cloud autoscaling solutions that are out there? The opportunity cost of spending time figuring out why only 29 workers are receiving requests over adding new features that generate more revenue, seems like a quick decision. Personally, I just start off with that now in the first place, the development load isn't any greater and the solutions that a…
containers would've solved it one process per container, easy peasy
This is what they did, but because they didn't need to schedule other jobs on the same machine, kubernetes or even docker would be overkill.
In this case, simple VM orchestration seems like a fine solution.
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#24use PHP ;)
So much this. Practically any other option is better than Python for web development if you're looking for performance.
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#25Kinda funny they decided paying a ton of money to aws was ok but paying for nginx plus was not
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#26Earlier quoted context omitted.
So much this. Practically any other option is better than Python for web development if you're looking for performance.
By this logic, why not Java, C++, Rust, Go, C#? They’re all web-capable and blow the doors off PHP, Python, etc.
The "blame our co-founder for the choice" bit is exactly what that graph about the cost of defects vs how early they are fixed is talking about.
If they had just picked Go or Java right at the start they wouldn't have had to expend all this engineering effort to get to a still-not-very-good solution.
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#27Earlier quoted context omitted.
...said a stranger on the internet without any sources to back up this claim.
only one data point though, but... https://redmonk.com/rstephens/2021/08/05/top-20-june-2021/
Javascript
Python
Java
PHP
C#
But is it about web?Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#28Kinda funny they decided paying a ton of money to aws was ok but paying for nginx plus was not
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#29Performance is the only thing that is holding me back to consider Python for bigger web applications. Of the 3 main languages for web dev these days - Python, PHP and Javascript - I like Python the most. But it is scary how slow the default runtime, CPython, is. Compared to PHP and Javascript, it crawls like a snake. Pypy could be a solution as it seems to be about 6x faster on average. Is anybody here using Pypy for…
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#30If it is just a backend, why not port it over to one of the myriad of cloud autoscaling solutions that are out there? The opportunity cost of spending time figuring out why only 29 workers are receiving requests over adding new features that generate more revenue, seems like a quick decision. Personally, I just start off with that now in the first place, the development load isn't any greater and the solutions that a…
Author here. We do and did use autoscaling heavily but at a certain scale we just ran out of headroom on the smaller instance types we were using. Jumping to a much larger instance types meant that we will likely never run into those headroom issues again, plus solves other problems like faster spin up, better sidecar connection pooling and allows for a much higher hit rate on per instance caching.