-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/02/2011 04:38 AM, Simon Slavin wrote: > Python is a bytecode language.
That isn't relevant in this case. The code that interfaces Python to SQLite is written in C. The amount of Python bytecode involved in this benchmark is irrelevant. On 06/02/2011 12:55 AM, Dominique Pellé wrote: > However, for a benchmark, it's best to avoid things that > can be trivially optimized. I don't know how the python > code translates into SQLite C API. In this particular case the OP is unable to modify the Python SQLite binding and what is trying to be established is why the performance differs, not the optimum sequences of code. That is why it is important to make sure that they are measuring exactly the same thing before investigating the massive difference in run times. (Incidentally I am the author of a "competing" Python SQLite binding and hence know exactly which SQLite API calls result from bits of Python hence being very pedantic about getting these tests the same.) Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk3n1XEACgkQmOOfHg372QTINACgsnRCkY6k6FQJQ0zOjHQUcCxj ryEAnj+2dk8eUYtbImaEfwXAWSQzlyyU =TTPX -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
