[
https://issues.apache.org/jira/browse/JSPWIKI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673582#action_12673582
]
Kurt Stein commented on JSPWIKI-498:
------------------------------------
Ok 2 Issues.
First. This is a really heavy bottleneck for performance. If there is any way
to avoid the Interface I will do so. But I don´t see the point. And I really
want a fix for 2.8 Versions (Saying that for JSPWiki Community because my
Wiki-Server has the fix and the search is running like a leopard)
Thus I need to pass these 2 additional paramters/variables to the
LuceneSearchprovider. This leads to the second Issue. I can avoid using the
wikiengine find(String,int,int) method. So do you want me to call the
searchmanager directly from ajaxsearch.jsp and search.jsp ?
I will checkout your JPSwiki Styles but personally I dont like the linebreak in
methodcalls (as I am working with a 22" Flatscreen -overview is not a issue)
PS: The stopwatch in search.jsp import can be removed. I think it is some
legacy from my tests for finding the bottleneck. Can you please specify which
paramters don´t adhere the standards?
> 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, patch_lucene_search_2.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.
