Advsearch Addon - any performance issues?

Hi everyone,

I am planning a project that requires a form that should search through a group of resources including their TV values. I was reading the documentation for Advsearch http://modx.com/extras/package/advsearch and was wondering if anyone had some experience using this and if the performance of this add on is ok. I would be searching through around 50 resources, each with like 10 TVs, but I will only be searching through 3 of them.

Thanks!

Quote from: sonicpunk at Nov 22, 2012, 04:53 AM

Hi everyone,

I am planning a project that requires a form that should search through a group of resources including their TV values. I was reading the documentation for Advsearch http://modx.com/extras/package/advsearch and was wondering if anyone had some experience using this and if the performance of this add on is ok. I would be searching through around 50 resources, each with like 10 TVs, but I will only be searching through 3 of them.

Thanks!

hi, you should be ok.
I have a lot more resources >1000 and lot's of tv's. AjaxSearchAdvSearch take ~2-3 sec to output the search result. [ed. note: emmanuel last edited this post 13 years, 10 months ago.]

Our latest project (revo 2.2.5) holds about >5000 resources in 4 contexts, each has at least two TVs attached. Running a search with AdvSearch (not AjaxSearch) takes max 0.5-0.8 seconds.
So there should be no problems with your site.

Thanks for this info! Wow, you guys have tons of resources going on!!! Nice to hear that MODX still performs well under those conditions. I did decide to make my own custom table though for the information using MIGXdb
http://rtfm.modx.com/display/ADDON/MIGXdb

Quote from: sonicpunk at Nov 26, 2012, 05:09 AM

Thanks for this info! Wow, you guys have tons of resources going on!!! Nice to hear that MODX still performs well under those conditions.

This system holds an import of previous news articles (about 9 years) spread across 4 contexts. And MODx has absolutely no problem with this huge load. )

Well, I might be wrong, but I noticed that the overall performance goes down the drain if your results_tpl contain lots of TVs to be displayed (20+).

Example:

Paginated facet search over 150 resources with 7 TV search fields and a free text search field (only vs. pagetitle) and a limit of 12 results per page.

If I add/remove includeTVs, I get very different results:

with includeTVs=`add 20 tvs here` = 10,7471 seconds.
without any TVs = 1,6676 s.

I also noticed that caching while moving between different result pages didn't work quite right.

In the end I had to twaek core/components/advsearch/model/advsearch/advsearch.class.php. Now it returns a placeholder containing a comma seperated list of all resources displayed on the current results page which I use in a subsequent getResources call.

This strategy takes less than 1 second for a total of less than 3 seconds which is still not very fast, but fine for now. Also caching seems to be working better.

Does anyone have similar issues?

Regards,

pepebe