Le lundi 8 septembre 2014 08:33:39 UTC+2, Naoki INADA a écrit : > > > On Monday, September 8, 2014 2:04:26 PM UTC+9, Naoki INADA wrote: >> >> > >> > Naoki, >> > >> > Are you aware of performance benchmarks comparing your MySQLdb1 fork >> and >> > mysql-connector-python? >> > > I've posted quick benchmark: > https://github.com/methane/mysql-driver-benchmarks > > Most heavy part of MySQL Driver is parsing packet. > There are (number of columsn) descripter packet and (number of columns * > number of rows) result packet in query response. > > On PyPy, packet parsing is faster after JIT warmup. > MySQL-Connector/Python reads from socket packet by packed. It makes many > system call. > PyMySQL uses buffering for faster receiving. >
Great, 8-9x difference in favor of the C implementation (which might be expected). That's a clear sign for me that we should continue using primarily the C version. That doesn't mean we shouldn't make efforts to support at least one Python-only driver (as asked in #12500). > About your fork, do you plan to maintain it in the middle/long term? I > saw > > that issues were not enabled on your Github repo. Is it on purpose? > What's > > the plan about bug tracking of your fork? > > > > Thanks for pointing it out. I've enabled github issue. > > I'll maintain mysqlclient-python until MySQLdb1 development is restarted. > Since I hope MySQLdb1 and mysqlclient-python merged someday (like > setuptools and distribute were merged), > I don't want to implement new feature. > 'maintain' means bugfix, support new Python, new libmysqlclient and > new OS, etc... > That makes sense. Tim, Florian, would it be possible to switch to that fork on the CI server (both for Python 2 and 3) for MySQL? Then of course, if all goes well, we would need to update our documentation. Claude -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7487c9c9-0b46-4e84-8203-7841ab0b0bba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
