Thank you for the clarification. I was wondering if I missed something with the command line or Python interface. I will stay tuned for the sqlite3_db_status method in future releases. ________________________________________ From: [email protected] [[email protected]] on behalf of Roger Binns [[email protected]] Sent: Tuesday, August 28, 2012 12:10 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] How to determine the effective cache size
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28/08/12 11:46, Foster, Kristina (CIV) wrote: > I set the pragma cache_size to 64 GiB per the online documentation. You may want to check that using SQLite's cache is actually beneficial. The operating system will also be doing caching so having data cached in memory twice isn't going to be that big a benefit. You can usually improve performance by making SQLite do less work. That involves careful tuning of queries and using the EXPLAIN/EXPLAIN QUERY PLAN commands. pysqlite/sqlite doesn't expose the sqlite3_db_status method as explained by DRH. I'll add it to the next release of APSW which will come out with the next SQLite release. (Disclosure: I'm the APSW author) APSW also includes a tracer tool which can be used without modifying your app. It is extremely useful to work out what is happening with an app that includes a lot of SQLite work scattered all over the code: http://apidoc.apsw.googlecode.com/hg/execution.html#apsw-trace Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlA9F6sACgkQmOOfHg372QRqmQCglP1C9aWM6aSSWv6CSqm4wTib +G8AoOKQuYd/dbmqsDdAh37YLURKHELu =UsnU -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
