On Tue, 14 Jun 2016 01:04:27 +0100 Simon Slavin <slav...@bigfraud.org> wrote:
> Got the principles ? Right. Now here's the procedure: > > 1) Delete all indexes. > 2) Run ANALYZE. > 3) Run your application. > 4) Note the SQLite command which takes the most annoyingly long time. > 5) Work out a good index which will fix the problem. > 6) Create the index. > 7) Repeat from step 2. > > When your application runs fast enough not to annoy you, you're done. If > you're not willing to do step (1), don't bother with anything else. > Great algorithm I use all the time. But you missed one small but very important detail: "When your application runs fast enough... **on the slowest possible computer you can run it** ...you are done." Neglecting this detail will always result yo sluggish programs on the average user computer. That is why I am using netbook class PCs and 5..10 years old desktop machines for testing my applications. -- http://fresh.flatassembler.net http://asm32.info John Found <johnfo...@asm32.info> _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
