Reining in the thundering herd: Getting to 80% CPU utilization with Django
1–10 of 139 posts
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#2* use uWSGI (read the docs, so many options...)
* use HAProxy, so very very good
* scale python apps by using processes.
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#3Good article though! I’ve dealt with these exact issues and they can be very frustrating.
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#4The 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 are out there are quite good.
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#5Of 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 Django?
Did Clubhouse document somewhere if they are using CPython or Pypy?
Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#6Re: Reining in the thundering herd: Getting to 80% CPU utilization with Django
#7use PHP ;)