Show HN: 1M rows/s from Postgres to Python

Re:Show HN: 1M rows/s from Postgres to Python by sametmax on Friday August 05, 2016 @02:54AM (#12230503)

The tone used is indeed not the proper one, but while I'm a big asyncio advocate, I think it would be beneficial if you would split your project in 2, separating the IO from the rest (like hyper does https://github.com/Lukasa/hyper).

The rational being:

- Python is not just async. It currently majoritarly sync. A lot of the community would benefit from your awesome project; - You'd have contrib from the async and sync community; - async may sometime not be worth it for db (http://techspot.zzzeek.org/2015/02/15/asynchronous-python-an... - some people will prefer to use threads or gevent; - you will see compat plugin created for current ORM;

That aside, I will use your project as is, since I'm deep in asyncio these days. Thank you.

[ Parent | on HN ]

Re:Show HN: 1M rows/s from Postgres to Python by 1st1 on Friday August 05, 2016 @09:50AM (#12232288)

> I think it would be beneficial if you would split your project in 2, separating the IO from the rest (like hyper does https://github.com/Lukasa/hyper).

I'd like to do that, but we don't have resources. If we had a couple capable devs volunteering on the GH to do this, I'd be glad to review patches and guide the development.

[ Parent | on HN ]

Re:Show HN: 1M rows/s from Postgres to Python by sametmax on Sunday August 07, 2016 @01:44PM (#12242837)

I get that. I have the same problem. And it's not just the ressources, what you need are skilled enough ressources, and that's even harder.

[ Parent | on HN ]