[
https://issues.apache.org/jira/browse/JSPWIKI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673592#action_12673592
]
Janne Jalkanen commented on JSPWIKI-498:
----------------------------------------
Yupyup, we do recognize this as a problem, but unfortunately there are some
ground rules we *have* to follow, or else we will simply lose the ability to
maintain the code. One of these are the code style instructions; the other one
is maintaining the compatibility rules. For example, if someone has written
their own SearchProvider, and we casually break the interface, they will have
to fix it in order to take a new minor release into use. In many corporate
environments, this may be difficult.
One possibility is to create a PaginatingSearchProvider interface, which has
the findPages(String,int,int) method, and have LuceneSearchProvider implement
that in addition to the regular SearchProvider interface. SearchManager can
then provide a findPages(String,int,int) method which checks whether the given
SearchProvider implements this PaginatingSearchProvider, and functions
accordingly.
And yes, the JSP files should call SearchManager directly.
> 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.
