On Wed, Jan 5, 2011 at 12:42 PM, Peter <peter at
somborneshetlands.co.uk>wrote:
> I have a Python web application that I am converting to use SQLite3 for
> local deployment instead of PostgreSQL to make it simpler to install.
>
> Some queries run up to 50 times slower using SQLite.
We can probably help you better if will post your entire schema, including
all table, index, view, and trigger definitions, in addition to the query
that is giving your trouble. Even better would be for you to run the
sqlite3_analyzer.exe utility over your database and send that result too, so
that we can get an idea of how much data is in your database and how it is
distributed.
<snip>
--
D. Richard Hipp
drh at sqlite.org
<snip>
Sorry, I assumed everything you needed to know was in the database that
I gave a link to: http://somborneshetlands.co.uk/things/sss-mini.zip
I'll sort out a text schema tomorrow.
I've run sqlite3_analyze and attached the result to this. I'm running on
a Linux box BTW - Arch-Linux if it makes any difference.
Setting the cache size and default cache size to 100000 pages made no
noticeable difference.
--
Peter Hardman
'For every complex problem there is a solution that is simple,
straightforward - and wrong'
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
