Hi Roger, Many thanks for your feedback, much appreciated ;-)
But why would that happen on Solaris and not Debian? Also, how would I pass the -D flags? Do I do that when I compile SQLite? Thanks again Lynton -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Roger Binns Sent: 20 November 2010 07:31 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] SQLite really SLOW on Solaris? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/20/2010 07:12 AM, Lynton Grice wrote: > On Debian it processes a couple hundred messages per second, on Solaris > using the SAME code it does like ONE message per second. One possible cause is the busy handler but this only applies if you have concurrent access to the file and have set a busy timeout. The default SQLite busy handler keeps trying again and if it fails sleeps, repeating the process. It will sleep for longer and longer periods until the overall busy timeout period has expired. If you do not provide any -D flags then the call used to do the sleeping has a granularity of one second - ie even if SQLite wants to sleep for 50ms it will sleep for one second. If you have the usleep() function and supply - -DHAVE_USLEEP then microsecond resolution sleeps are available. These are the sleep intervals in milliseconds that sqliteDefaultBusyCallback tries when USLEEP is available: { 1, 2, 5, 10, 15, 20, 25, 25, 25, 50, 50, 100 } Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzoBeIACgkQmOOfHg372QTXHQCfQ3HIoXF5FcqP9AttZ7gNdPEZ IKYAoMVuIqoSa4e08nsbVQk5ABWZdq1G =+TOO -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
