Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-11-19 Thread Luca Sbardella
On 18 November 2016 at 23:09, Yury Selivanov wrote: > Also, are you using uvloop or vanilla asyncio? Try to benchmark vanilla > first. And if you have time, please try to test different combinations on > vanilla asyncio: > > Python 3.5 + vanilla asyncio > Python 3.6 +

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-11-18 Thread Yury Selivanov
> On Nov 18, 2016, at 6:16 PM, Luca Sbardella wrote: > > Running 3.6-dev from travis, currently b4+. > No debug mode, that is an order of magnitude slower ;-) FWIW I found that I can’t really trust the build times on travis for measuring any kind of performance

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-11-18 Thread Luca Sbardella
> > > > That shouldn’t happen. Are you sure you aren’t running them in debug > mode? Try to comment out imports of ‘_asyncio’ in futures.py and tasks.py > and run benchmarks in 3.6 to compare Py Futures to C Futures. > > Also, which Python 3.6 version are you using? Please try to build one >

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-11-18 Thread Yury Selivanov
Also, are you using uvloop or vanilla asyncio? Try to benchmark vanilla first. And if you have time, please try to test different combinations on vanilla asyncio: Python 3.5 + vanilla asyncio Python 3.6 + vanilla asyncio Python 3.6 + Py Future + Py Task Python 3.6 + Py Future + C Task Python

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-11-18 Thread Yury Selivanov
> On Nov 18, 2016, at 5:53 PM, Luca Sbardella wrote: > > But tests taking 1.48 longer to run on average! > Anything I should know about 3.6 and performance? > That shouldn’t happen. Are you sure you aren’t running them in debug mode? Try to comment out imports of

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-11-18 Thread Luca Sbardella
But tests taking 1.48 longer to run on average! Anything I should know about 3.6 and performance? On 18 November 2016 at 22:42, Luca Sbardella wrote: > Pulsar's tests are now run against 3.6-dev and all passing. > Nice! > Getting used to the C Future ;-) > > On 13

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-11-18 Thread Luca Sbardella
Pulsar's tests are now run against 3.6-dev and all passing. Nice! Getting used to the C Future ;-) On 13 October 2016 at 06:37, INADA Naoki wrote: > Thanks, Ben. > > Both are very helpful information! > > On Thu, Oct 13, 2016 at 2:25 PM, Ben Darnell

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-10-12 Thread INADA Naoki
Thanks, Ben. Both are very helpful information! On Thu, Oct 13, 2016 at 2:25 PM, Ben Darnell wrote: > [+async-...@python.org, which is the new home for these kinds of > discussions] > > Tornado's tests are now failing on nightly with "TypeError: can't send > non-None value

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-10-11 Thread INADA Naoki
> If you have asyncio based project, and it uses Travis-CI, > please add "nightly" to your .travis.cnf [2]. > > [2] > https://docs.travis-ci.com/user/languages/python/#Choosing-Python-versions-to-test-against Travis changed the "nightly" version to 3.7 Now "3.6-dev" is for Python 3.6beta (Still

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-10-10 Thread Ludovic Gasc
Hi Naoki, Thanks a lot for that. FYI, we'll do a sprint code during PyCON-FR to upgrade AsyncIO test suite in TechEmpower Benchmarks, to include new interesting efficiency improvements from community (uvloop, asyncpg...). Our todo-list: https://github.com/Eyepea/FrameworkBenchmarks/issues We'll

Re: [python-tulip] Python 3.6b2 will have C implemented Future

2016-10-09 Thread Nickolai Novik
Hi At aio-libs (https://github.com/aio-libs/) projects: aiosmptpd, aiomysql, aiorwlock, aiohttp_sessions, aiohttp_security, aiohttp_debugtoolbar, aiohttp_admin, aiohttp_mako use "nightly" python version on Travis-CI. So far all builds are green. Hopefully in nearest future we will be able to test