Improve Search Results and Performance With MySQL Full Text
01-05-2012, 05:30 PM
#1
Improve Search Results and Performance With MySQL Full Text
So vBulletin has two options for searching, one is its internal index, and one is a mysql fulltext search. Larger forums MUST use the mysql fulltext search if you want the searching to be effective. By default, vbulletin has its internal search enabled.
Here is a quick rundown of the two:
Fulltext
Pros
Less PHP resources used because the indexing takes place in MySQL.
No need to maintain the postindex and word tables which can take up a lot of space.
Natural Language and Phrase searching is available.
Can Sort by relevancy for better results
Default search in vBulletin's latest versions.
Can support more searches per minute.
Searches can take better advantage of MySQL's query caching.
Cons
Less Flexible Indexing, especially on Shared Servers. Changing parameters requires shutting down MySQL, dropping indexes and rebuilding them.
Fewer control parameters within vBulletin.
Rigid Stopword list as an external file.
vBulletin Builtin Search
Pros
Not reliant on your MySQL version.
Can be easily manipulated in the Admin CP including adding words under the minimum character limit or changing that limit.
Cons
Resource heavy, especially building the index.
Indexing must be done before post is inserted to database and can result in errors on overwhelmed systems.
Search Results can cause database errors if there are too many hits.
Large tables must be maintained manually for proper usage.
No Natural Language or Phrase based searching.
Easy to bring down large boards with multiple searches.
Here is a page that can help set up this search function:
https://www.vbulletin.com/docs/html/main/search_type
Here is a quick rundown of the two:
Fulltext
Pros
Less PHP resources used because the indexing takes place in MySQL.
No need to maintain the postindex and word tables which can take up a lot of space.
Natural Language and Phrase searching is available.
Can Sort by relevancy for better results
Default search in vBulletin's latest versions.
Can support more searches per minute.
Searches can take better advantage of MySQL's query caching.
Cons
Less Flexible Indexing, especially on Shared Servers. Changing parameters requires shutting down MySQL, dropping indexes and rebuilding them.
Fewer control parameters within vBulletin.
Rigid Stopword list as an external file.
vBulletin Builtin Search
Pros
Not reliant on your MySQL version.
Can be easily manipulated in the Admin CP including adding words under the minimum character limit or changing that limit.
Cons
Resource heavy, especially building the index.
Indexing must be done before post is inserted to database and can result in errors on overwhelmed systems.
Search Results can cause database errors if there are too many hits.
Large tables must be maintained manually for proper usage.
No Natural Language or Phrase based searching.
Easy to bring down large boards with multiple searches.
Here is a page that can help set up this search function:
https://www.vbulletin.com/docs/html/main/search_type
01-06-2012, 10:54 AM
#7
If I had access to the closed "DIY: How to Search" sticky thread I could provide a number of helpful tips.
Of course the biggest problem of all has no real solution; none of the clueless noobettes on this site would any more look at it than any other sticky or information thread here.
Which BTW the DIY area needs another technical question thread flushing ...
.
Of course the biggest problem of all has no real solution; none of the clueless noobettes on this site would any more look at it than any other sticky or information thread here.
Which BTW the DIY area needs another technical question thread flushing ...
.
Last edited by TeamRX8; 01-06-2012 at 03:48 PM.
Thread
Thread Starter
Forum
Replies
Last Post
Touge
Canada Forum
0
07-18-2015 05:41 PM
