From: <km...@we...> - 2007-02-27 16:07:57
|
Hi, I am currently testing a search form which invokes a XQuery. This query uses the fulltext index with the &= operator. If I concatenate the original query string with "!" and invoke the query I got 100% CPU usage and a memory increase of 50MB. Is this a known bug or do I have overlooked something? The query took 202241 ms, the same query without "!" took 1121 ms BTW, I use eXist 1.1.1. Kai |
From: Wolfgang M. <wol...@gm...> - 2007-02-27 16:12:48
|
Hi, > I am currently testing a search form which invokes a XQuery. This query uses > the fulltext index with the &= operator. If I concatenate the original query > string with "!" and invoke the query I got 100% CPU usage and a memory > increase of 50MB. Is this a known bug or do I have overlooked something? It certainly is a bug, though I can't reproduce it with the trunk version right now. I'll recheck on 1.1.1. Wolfgang |
From: <km...@we...> - 2007-02-28 15:41:31
|
exi...@li... <> wrote: > Hi, > >> I am currently testing a search form which invokes a XQuery. This >> query uses the fulltext index with the &= operator. If I concatenate >> the original query string with "!" and invoke the query I got 100% >> CPU usage and a memory increase of 50MB. Is this a known bug or do I >> have overlooked something? > > It certainly is a bug, though I can't reproduce it with the trunk > version right now. I'll recheck on 1.1.1. > I am not sure if the following has something to with the above bug. There is another query uses the fulltext index with the &= operator where we can observe the following query execution times: Hydraulic Power System: 721ms Hydraulic System: 791ms *draulic Power System: 1672ms Hydraulic Power Sys*: 1021ms Hydraulic*System: 310ms (no results) Hydraulic * System: 32768ms and more!!! I know that "Hydraulic * System" doesn't make sense because "Hydraulic System" delivers the same result set. But maybe it helps solving the problem. Kai |
From: Pierrick B. <pie...@cu...> - 2007-02-28 16:20:20
|
Hi, Kai Mutz a écrit : > I am not sure if the following has something to with the above bug. I don't think so. All these results seem to be normal. > Hydraulic Power System: 721ms 3 tokens search. More restrictive than the following... > Hydraulic System: 791ms 2 tokens search. > *draulic Power System: 1672ms Initial truncature : scan all over the fulltext index > Hydraulic Power Sys*: 1021ms Right truncature, index scan from "sys" (your fulltext index is probably case insensitive). "Zys*" would have probably been more efficient here ;-) > Hydraulic*System: 310ms (no results) I doubt you have this token in your data, have you ? > Hydraulic * System: 32768ms and more!!! To be understood as : Hydraulic [every token in the full text index] System Cheers, -- Pierrick Brihaye, informaticien Service régional de l'Inventaire / DRAC Bretagne mailto:pie...@cu... / tél : +33 (0)2 99 29 67 78 Avez-vous lu http://usenet-fr.news.eu.org/fr-chartes/rfc1855.html ? |