Marian Aldenhoevel <[EMAIL PROTECTED]> writes: > > Hi, > > I have tried converting a program from a homebrew "database" to sqlite3 > for easier maintenance and hopefully better performance. While the > former is easily achieved, the performance is not making me happy. The > system is a "semi-embedded" small form-factor x86 machine with 128MB of > RAM booting and running off CF. OS is a 2.4.18-based linux built from > scratch. > > I have run several tests outlined below and I can't get decent > UPDATE-Performance out of my database. Apparently I am doing something > horribly wrong. Can someone enlighten me? .... > > Finally I repeated the test using a simpler table consisting only of the > column musttrans and 300000 records. Updating that took abount the same > amount of time. > > Ciao, MM >
Speaking as a non-indexed person ! from other posts here I would suggest it's the fact that you have an index on the field you are updating that takes the time. Remove the index on that field and see how long it takes. Some people have even suggested (in a non-flash-based system presumably) DROPping the index, doing the UPDATEs, then reindexing. Regards, MikeW _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users