>> Thanks Daryl, I was poking around a bit and ran into this: >> http://blog.zmok.net/articles/2006/08/14/full-text-search-in-ruby-on-rails >> >> Right now I'm running mysql on the backend (I gave up on Postgres and my >> mysql issues went away when I switched from 3.23 to 5) and assuming >> Instiki is doing a full text search using mysql that could be our >> problem. I don't know if there are any plans to add Ferret to Instiki...? >> > > Not that I know of, though I (and John Whitley) have been (very slowly) > trying to start working on the Instiki code base. > > Am I correct in thinking that your problem was fixed by adding a MySQL > full-text index? > I hesitate to say yes since I haven't done any performance metrics but I do know this. I added an index in mysql:
CREATE UNIQUE INDEX name_index ON pages (name); and for the first time one of my searches in my full (~15K) page database completed. I'll try to poke around a bit more and get something more definitive. The search still ran for a long time (15 seconds?) but I'm impressed that active record and/or mysql knew enough to use the index. I'm guessing ferret is a better (and db independent) solution though, but I haven't investigated that yet. What plans do you and John have for the code base? -John _______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
