I hope you didn't turn this off, we switched to sphinx for full text indexing. If its not working we need to fix it, not turn it off.
Yep, sorry, I switched back to Full Index.
Seems to work fine though?
Why did we switch to Sphinx? and how can we be sure it's not going to get disabled again and no one notice until the search gets bad enough?
MySQL is too slow when several searches occur at once, we saw widespread issues when Bing was using the search to index the website, but also when I tested it with a few concurrent searches. MySQL is not designed for this level of search/index, here are the stats from Sphinx:
collected 1276001 docs, 865.5 MB
sorted 143.9 Mhits, 100.0% done
total 1276001 docs, 865542064 bytes
So there is 143.9 million search terms being indexed. Services like google, ebay, amazon, etc... all use a full text search index such as Sphinx for datasets like this.
To avoid cPanel messing with it again I have created a system account for sphinx and configured a crontab for it, cPanel will not touch this account as it knows nothing about it.
Some more info on Sphinx (from
http://sphinxsearch.com/about/sphinx/):
- Indexing performance. Sphinx indexes up to 10-15 MB of text per second per single CPU core, that is 60+ MB/sec per server (on a dedicated indexing machine).
- Searching performance. Searching through 1,000,000-document, 1.2 GB text collection that we use for everyday development and testing runs at 500+ queries/sec on a 2-core desktop machine with 2 GB of RAM.
- Scalability. Biggest known Sphinx cluster indexes 25+ billion documents, resulting in over 9TB of data. Busiest known one is Craigslist, serving 300+ million search queries/day.