On Sun, May 8, 2016 at 11:07 AM, Yury V. Zaytsev <y...@shurup.com> wrote: > Hi Maciej, > > Thanks for the feedback! > > On Sun, 8 May 2016, Maciej Fijalkowski wrote: >> >> >> I would personally use something cffi-based, like this: >> https://github.com/andrewsmedina/mysql-cffi > > > Well, neither this seems to be supported by Django, nor it looks like it's > actively maintained... :-/ > >> Generally speaking all cpyext-based solutions will be slower (although >> these days I know MySQL-Python should indeed just work and not crash) than >> non-cpyext based solutions but depending on the application you might or >> might not care. > > > Okay, so I started out with CPython and I'll keep an eye on the load; the > plan is to bring up a second upstream to experiment with PyPy and see if > this is getting me anywhere. I will then either try the pure Python fork of > MySQL-Python, or the original and see if that's really the bottleneck.
For the record - if you are using django ORM, then the mysql binding is unlikely to be your bottleneck for accessing the DB. > > On a related note, has anyone tried binary wheels with PyPy, are they known > to work? Among other dependencies I have is for example Pillow; so far I've > been building binary wheels on a dedicated development server and deploying > them to the application server which doesn't have any complier > infrastructure installed. Will this simply work for PyPy? It should. > > > -- > Sincerely yours, > Yury V. Zaytsev _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
