> are you sure you added my fix? here my phonelog.db is 100k and it only > takes ~10 seconds (first test was with a trimmed down log). I am on shr-testing (don't know if the database structure changed in unstable???)...can that be a reason? I am ready to switch to unstable but non-working wifi was a deal-breaker
> Weird... Maybe try > SELECT * FROM calls; > in sqlite3 and see how much time it takes... if more than a milisecond, I am not much aware of sqlite (even with SQL), anyways with .timer ON 'select * from calls;' gives CPU Time: user 0.400000 sys 0.225000 (thats the only time measurement I could do). There are 262 records that are printed over Wifi, so scrolling text took some 1.5 seconds (I guess thats useless info) > that may be the issue ;) anyhow I'll optimize pyphonelog's queries sometime, > hopefully tomorrow, and will try to make everything quicker... in general > this db could use some more indexes. (not too many, but a bit more). I can try a bit of tinkering at my end... BTW, because I am using shr-testing, can I get phonelog (the main python file)...so that I can update it with your latest changes --Vikas _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
