[
https://issues.apache.org/jira/browse/JSPWIKI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672568#action_12672568
]
Kurt Stein commented on JSPWIKI-498:
------------------------------------
The problem is as long as I don't get the trunk started (Because of all the
pending JCR stuff) to see what I am doing I prefer to work on the branches.
So i will make my patch working on JSPWIKI_2_8_BRANCH.
So you want the JSP-Page to call the Searchmanger and not the wikiengine to
perform the search?
In general I think it would be best to make the call from AjaxSearch.jsp and
Search.jsp the same way to reduce duplicate code.
> 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.1
> Environment: Win 2003 on XEN-Server, 3 GB RAM, 4 x Intel Xeon 2Ghz
> Reporter: Kurt Stein
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
