Re: [pysqlite] Performance degradation

I made further tests using the build-in sqlite3 module of the official
Python 2.5 and 2.6 Windows binaries:

Python 2.5:
  sqlite3.version: 2.3.2, sqlite3.sqlite_version: 3.3.4
  1.109 sec (avg. of 10 runs)

Python 2.6:
  sqlite3.version: 2.4.1, sqlite3.sqlite_version: 3.5.9
  1.117 sec (avg. of 10 runs)

So quite the same performance despite the different SQLite versions
used.  But both Python versions were compiled using the MS compilers.


On Tue, Nov 25, 2008 at 10:27 AM, Gerhard Häring <[email protected]> wrote:
>
> I tried to find out if there's a general performance degradation for this
> use case from 2.4.1 to 2.5.0:
>
> 2.4.1:
> took 6.8649045229 seconds - average 10 runs
>
> 2.5.0:
> took 6.8972679615 seconds - average 10 runs
>
> Considering this was not a completely idle system, I'm confident now that
> nothing changed at all performance-wise between these two versions.
>
> I used the same SQLite versions and built using amalgamation both times.
>
> My first guess would be different SQLite versions used in your case, I don't
> think different compilers make such a big difference.
>
> Is there anybody here that could est speed of pysqlite compiled with Visual
> Studio 2005 vs. gcc on Windows? I'll attach my quick test script. As
> apparently pysqlite doesn't make the difference, it should be possible to
> test that with SQLite binaries, too.
>
> -- Gerhard
>
> _______________________________________________
> list-pysqlite mailing list
> list-pysqlite-FR6EJeJVuqdwc357pe9rcyQmJico6nz3epZhswDD4dQ@public.gmane.org
> http://itsystementwicklung.de/cgi-bin/mailman/listinfo/list-pysqlite
>