Thanks for sharing the results! It seems to reaffirm the results obtained in my benchmarks, which is a good thing ;)
I agree that uWSGI can be somewhat difficult to setup and I also did not see any great performance differences between TCP sockets and UNIX sockets.
Where you not able to predict the memory usage of the uWSGI setup as well? I did not really experiment with multiple workers but I noticed it to be on the low side.
Regarding memory usage when using uWSGI I was unfortunately not able to measure it. The tools I used didn't make it easy enough. I did look at some outputs but didn't write it down but from what I can remember it barely moved even at high number of workers. I thought it was my fault but perhaps it was that memory efficient.
Comment
Thanks for sharing the results! It seems to reaffirm the results obtained in my benchmarks, which is a good thing ;)
I agree that uWSGI can be somewhat difficult to setup and I also did not see any great performance differences between TCP sockets and UNIX sockets.
Where you not able to predict the memory usage of the uWSGI setup as well? I did not really experiment with multiple workers but I noticed it to be on the low side.
Replies
Regarding memory usage when using uWSGI I was unfortunately not able to measure it. The tools I used didn't make it easy enough. I did look at some outputs but didn't write it down but from what I can remember it barely moved even at high number of workers. I thought it was my fault but perhaps it was that memory efficient.