Duh, thanks. I indexed my database, enabled mysql full text, cleared the vB search index, dropped the word table, wrote in the quick hack for more optimized search by user name. All seems to be running smoothly (on a development server). I think resetting the mysql minimum word length from 4 down to at least 3 is going to be pretty standard procedure too.
But I guess the question begs... what's the benefit? I'm reading about some performance issues here on big boards. We have a small board (150K posts). I don't have the luxury of load testing this implementation, so it would be sort of trial by fire to launch it live. Are there any basic comparisons between vB search and mysql full text that I could measure right now? Query response times? Memory useage? Details?
If all of this just serves to reduce the size of the overall database, and eliminate the hassle of maintaining the cumbersome vb search index... and all other things from the user perspective remain equal... then I'm not so sure if it is really necessary at this point for us. Comments?
In my informal tests, fulltext is faster than the cumbersome vb search index.
Zachery, just a follow-up... after implementing this "hack" what is your recommendation for ACP settings in the "Message Searching Options" and "Message Searching Relevance" options areas? Are any of these settings relevant when running with full text search? Would it make sense to turn anything off or adjust anything there to achieve greater optimization? Also, I assume you recommend clearing the old vb seach index, and for the supremely confident dropping the vbword table? Thanks.
Freddie... is it possible to have some quick fix to speed up the current full text search option? I'm available to test things, as, as of now, I was forced to disable and there's no way I'm gonna reindex everything under the old option (yes, I emptied the search table, call me stupid, I know I am...). 2.5 million posts board, with 250+ users online...
Ahhh... with 2.5 mil posts, reindexing would take a couple of days.
Maybe install the vB3 fulltext search hack - it does work, and you won't have to reindex, and still utilize the fulltext (since you already have fulltext indexes on the post table).
Freddie... is it possible to have some quick fix to speed up the current full text search option? I'm available to test things, as, as of now, I was forced to disable and there's no way I'm gonna reindex everything under the old option (yes, I emptied the search table, call me stupid, I know I am...). 2.5 million posts board, with 250+ users online...
Ditto, I'd be great if we could have a quick fix for this. I did what gorman did with the search table and now I'm stuck.
Ditto, I'd be great if we could have a quick fix for this. I did what gorman did with the search table and now I'm stuck.
I re-indexed!
But on my first go it escalated the load so high that my hosting company rebooted thinking something got out of hand.
I had to modify the admincp code so that the redirect paused 20 seconds... it took over 2 days to re-index all of my boards doing 250 posts with 20 second pauses.
What joy!
I think I'll stick with the old method until this is proven.
But on my first go it escalated the load so high that my hosting company rebooted thinking something got out of hand.
I had to modify the admincp code so that the redirect paused 20 seconds... it took over 2 days to re-index all of my boards doing 250 posts with 20 second pauses.
What joy!
I think I'll stick with the old method until this is proven.
If you did the fulltext system you didnt need to reindex, mysql did that on its own
Erm, Zachery? I haven't applied the 0.3 upgrade to my forum yet, but I did on a client's board and nowhere do I see in VB Options "Version Info and Other Untouchables". His is a totally unhacked board too (so far anyway). Any ideas?
Erm, Zachery? I haven't applied the 0.3 upgrade to my forum yet, but I did on a client's board and nowhere do I see in VB Options "Version Info and Other Untouchables". His is a totally unhacked board too (so far anyway). Any ideas?