[TYPO3] indexed_search can congest MySQL server for long time

R. van Twisk typo3 at rvt.dds.nl
Sat Feb 24 14:07:42 CET 2007


Hey Christian,


I believe that indexed search was never intended for searching large 
amouth of data,
although indexedSearch is good for smaller sites.
I would suggest look into search engines like mnogosearch or
htdig to index your site.

Ries
> Hi,
> I'm having trouble with indexed_search. I'm using it on a site which
> has lots of text. The database is only about 350MB (a dump would be
> about 500MB) big but it takes ages to search for anything. If I search
> for one word that is rather prominent on the site, the search takes
> about 1 min! I have recreated my index which seems to help a bit but not
> much.
>
> However, my big problem is that with several simultaneous searches, you
> can congest the MySQL server for long time (apparently up to 30 min or
> so). During that time my server load can go up to 50 because MySQL is
> sucking 95% of the CPU. It is not exactly a slow box and I've never had
> problems with any other services. However, sometimes I've had to kill
> MySQL to get the box to run properly again. Has anyone had this problem
> before? The search on typo3.org seems to be a lot faster. Is it
> possible to tweak MySQL so that it does not run into this? At the
> moment this problem might even expose me to DoS attacks!
>
> Cheers,
> Christian
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>   


-- 
Ries van Twisk
Freelance Typo3 Developer
=== Private:
email: ries at vantwisk.nl
web:   http://www.rvantwisk.nl/freelance-typo3.html
skype: callto://r.vantwisk




More information about the TYPO3-english mailing list