Hi, I'm having a performance issue with filtering large documents using cts:search. What I found out looks roughly like the following code.
let $boostedQuery := cts:boost($hugeGeneratedQuery, $rangeQueryWithScoreFunction) let $result := cts:contains($largeDocument, $boostedQuery) With a really large document this took 2.1 seconds. Now, when I use $hugeGeneratedQuery in the second line, instead of the $boostedQuery, it looks like this: let $result := cts:contains($largeDocument, $hugeGeneratedQuery) Suddenly the filtering with cts:contains is now 60% faster. >From a logical point of view, the results should be the same, as boosting only affects the order. So, when using cts:contains, one could - as a workaround - use the matching query and not the boosted query. But this performance issue seems to affect cts:search too, when using "filtered" queries. Do you have any idea what I could do? Regards, Andreas -- Andreas Hubmer IT Consultant EBCONT enterprise technologies GmbH Millennium Tower Handelskai 94-96 A-1200 Vienna Mobile: +43 664 60651861 Fax: +43 2772 512 69-9 Email: [email protected] Web: http://www.ebcont.com OUR TEAM IS YOUR SUCCESS UID-Nr. ATU68135644 HG St.Pölten - FN 399978 d
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
