3 ms·
I see a lot of these types of blogs but I'm always left with the same questions. Did they not try using PyPy? Using LXC and PyPy would be my first step, not swa
by BuckRogers 11y ago
I see a lot of these types of blogs but I'm always left with the same questions. Did they not try using PyPy? Using LXC and PyPy would be my first step, not swapping out my stack. It just seems more sensible to me considering that Go as a platform isn't perfect either. Nothing is.
But I'd be hesitant to leave a massive, thriving ecosystem like Python (especially if on 2.7 which has everything). Win some things, lose some others when you can just adopt containers and PyPy and gain the benefits that Go has without losing Python's advantages.
- eloff 11y agoThey tried Cython first, so PyPy wouldn't have been faster than that. The big speedup for them was in making the code parallel, which is tricky in python and typically requires processes instead of threads and copying instead of sharing, either of which may eat most of the gains in this case.
- gcb0 11y agotheir problem was using weird and heavy frameworks. i wouldn't consider djangob for anything other than a heavily cached content site. seems like it's a company that just plow through problems. i bet whatever the problem is in go they will find only next week. python 2.7 and 3 have a marvelous, but not very well documented, multiprocessor module. it gives you more performance for that the cython and other shenanigans. but i guess using the existing tool right doesn't give promotions. ... yeah I'm making a lot of assumptions about then but that's just because I'm salty today. they should still learn to use python multiprocessing module. :)