Updating timestamp attributes 32-Bit vs. 64-Bit performance There is an issue concerning the 32-Bit vs 64-Bit performance of sqlite on update SQL. Ordinary update sql staements have been used to update the timestamp attributes on a database which holds sensordata of meteorological instruments. An exemplary statement is e.g. -- update sensordata set dataset_date = '2011-03-26 22:33:21' where dataset_no = 5284488; -- In the testcase 1098 different datasets of a table have been updated using this sql statement.
Hardware/software configurations used in the test were (1) Lenovo S10e Intel(R) Atom(TM) CPU N270 @ 1.60GHz 1.5GB RAM Ubuntu 10.04 i686 sqlite 2.8.17 (2) Dell 745 Intel Core2Duo, 2.13 GHz 4GB RAM Snow Leopard x86_64 sqlite 3.6.12 (3) Scenic Esprimo E5615 Athlon 64 3800+, 4GB RAM OpenSuSE 11.4 x86_64 sqlite 3.7.5 (4) Lenovo T61, Intek Core 2 Duo 2.0 GHz, 2GB RAM Ubuntu 10.04, x86_64 sqlite3 3.6.22 These 4 configurations gave the following performance results (the time in milliseconds is the average time for one of the update statements). (1) 12.2 msec (real) (2) 1.4 msec (real) (3) 150.0 msec (real) (4) 117.0 msec (real) The performance difference between Ubuntu 10.04 i686 on a Atom N270 1.6 GHz vs. Ubuntu 10.04 x86_64 on Core 2 Duo 2.0GHz is approx. a factor of 10, but in favor of the 32 Bit netbook. The performance difference of the same SQL in Mac OS X Snow Leopard x86_64 vs. Ubuntu 10.04 x86_64 ia approx. a factor of 100. Identical databases with identical SQL statements have been used in the 4 configurations. Sqlite has been installed from standard software repositories. Any help is greatly appreciated on how to solve this issue. -- Volker Jahns, vol...@thalreit.de _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
