On Fri, Mar 13, 2015 at 8:35 AM, INADA Naoki <[email protected]> wrote:
> >> IMO, When I really needs high performance (1000~ req/(sec*cores)), I > >> use Go in these days. > > > > From my point of view, Python is the best language to write business > logic. > > I hope to continue to find solutions to improve performance with Python > > instead of to regenerate a toolbox with another language. > > Agree. I'm waiting PyPy3 2.5.0 (compatible with Python 3.3) to run > asyncio on PyPy. > Yes, I've the same hope with PyPy because I've seen benchmarks like this: https://twitter.com/oberstet/status/550741713762136064 https://github.com/oberstet/scratchbox/tree/master/python/twisted/sharedsocket Especially theses results: https://github.com/oberstet/scratchbox/raw/master/python/twisted/sharedsocket/results.pdf I've no idea if it means that PyPy should be more performant than Go, nevertheless, if I arrive to have the half performance of an Nginx, it means I only need the double of servers to have the same performance. It's more acceptable that x10 or x100. BTW, if theses values become true with AsyncIO, nevertheless, it will be hard to convince people to use that, for most people, Python is slow. > > Go is best for networking middleware and micro~small services. > So I want to have common way to call Go from asyncio. > >From my point of view, it sounds a little bit a Frankenstein association. Nevertheless, maybe you're right in term of performances, compare to use something like Redis or ZeroMQ to have fast communications between your Go application and your Python. If you do something, I'm interested in to know your results. > > > P.S. I hope dropbox/pyston also support Python 3.4 and asyncio runs on it > too. > > I'm sad about both Google (Guido has been there) and Dropbox (Guido is > in now) haven't > moved to Python 3 yet. > I'm agree with you, nevertheless, I understand Dropbox's priorities if they have a lot of Python 2 code. Moreover, you certainly know we have some performance regressions between CPython 2 and CPython 3. I've spotted 2, 3 things, I'll publish that when I'll be sure to understand the problem. > > -- > INADA Naoki <[email protected]> >
