jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ichiro Furusato <ichiro.furus...@gmail.com>
Subject Re: [jira] [Closed] (JSPWIKI-498) Performance Issues with Lucene Index
Date Mon, 07 Jan 2013 01:09:48 GMT
I'd have to say that it's likely there's an installation/configuration issue
here, not a Lucene code issue. With even extremely large indices 30
seconds is not a typical response time, even if the index is being queried
twice.

My recommendation to the user would be to stop the server, delete the
index and let it be rebuilt, and make sure the server is not starved for
memory -- my own experience is that if one is seeing 30 second responses
there's a bottleneck somewhere, and it's probably not Lucene.

Ichiro

On Mon, Jan 7, 2013 at 6:28 AM, Harry Metske (JIRA) <jira@apache.org> wrote:
>
>      [ https://issues.apache.org/jira/browse/JSPWIKI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
>
> Harry Metske closed JSPWIKI-498.
> --------------------------------
>
>     Resolution: Incomplete
>
> no follow up unfortunately.
> Feel free to re-open is patches are there.
>
>> Performance Issues with Lucene Index
>> ------------------------------------
>>
>>                 Key: JSPWIKI-498
>>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-498
>>             Project: JSPWiki
>>          Issue Type: Bug
>>          Components: Default template
>>    Affects Versions: 2.8.4
>>         Environment: Win 2003 on XEN-Server, 3 GB RAM, 4 x Intel Xeon 2Ghz
>>            Reporter: Kurt Stein
>>             Fix For: FutureVersion
>>
>>         Attachments: lucene_search.patch, patch_lucene_search_2.txt, patch_lucene_search.txt,
screenshot-1.jpg
>>
>>
>> Our Wiki-Luceneindex has swollen to 33 MB and if someone searches words like "find"
he gets about 500 results. Only problem is, it takes about 30 seconds to complete the search.
>> I have looked a bit into the problem and there is something strange to me. JSPWiki
searches twice every query.
>> Once in search.jsp and afterwards in AjaxSearch.jsp.
>> The filteredList from search.jsp is written to the pagecontext but this information
is never read within the AjaxSearch.jsp. Thus AjaxSearch.jsp makes a second search.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message