Dan Kennedy wrote: > On 02/17/2011 05:41 AM, Iker Arizmendi wrote: >> Dan Kennedy wrote: >>> Can you make the database available for download? And >>> supply the exact query you are using too? I'd like to >>> know why this is. Thanks. >>> >>> Dan. >>> >> You can find a tarball of the DB file here: >> >> http://www.research.att.com/people/Arizmendi_Iker/geo.db.tgz >> >> This query runs in around 1.2 seconds: >> >> SELECT length(content) >> FROM locateme >> WHERE locateme MATCH 'newark OR new OR brunswick'; >> >> And this one in around 8.5 minutes: >> >> SELECT length(matchinfo(locateme, 'x')) >> FROM locateme >> WHERE locateme MATCH 'newark OR new OR brunswick'; >> > > The database uses a custom tokenizer - "stopwords" - so I can't > run the queries directly. If I dump the data into a regular fts3 > table using the default tokenizer and then run your queries with > 3.7.5 they both run in pretty much the same amount of time. Both > much quicker than 1 second on a Linux PC. > > There was a bug causing excessive calls to realloc() fixed a > little while ago, although from memory I don't think it would > have hit this case. The symptoms are similar though, so I could > easily be wrong on that. > > Suggest upgrading to 3.7.5 to see if that clears the problem. > > If you can get this slowdown with 3.7.5 and one of the built in > tokenizers, please post so I can look again. > > Thanks, > Dan.
Upgrading to 3.7.5 (from 3.7.4) did the trick. Thanks again! Iker _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users