There are multiple ways how you can improve search performance. For example you can change following parameters of search indexer: - respectDocumentOrder: If true and the query does not contain an 'order by' clause, result nodes will be in document order. For better performance when queries return a lot of nodes set to 'false'. - resultFetchSize: The number of results the query handler should initially fetch when a query is executed. Default value (Integer.MAX_VALUE) means all results. But realistically in most cases it doesn't make any sense to present user with more then say 500 results. So you might want to lower the value to speed up the search as well.
For other cases when you experience slow search you should actually look into what it is users are searching for and instead of blindly using simple search tag, write the query that would look only into the fields or parts of the site you want to make searchable for them. Cheers, Jan On Tue, 2008-08-05 at 02:08 -0700, spudnick wrote: > unfortunately the search queries also the metadata (with data like name of > creator, editor of page and so on). we're also experiencing long search > times :( > > > > Magnolia - User mailing list wrote: > > > > I am experiencing some problem with searches on a larger site. Say for > > example you have 5000+ pages in magnolia all created by superuser and > > you search for super - the search takes an awful long time. Am I doing > > something wrong or is this normal behavior? > > > > Thanks > > > > Ruben Reusser > > > > ---------------------------------------------------------------- > > for list details see > > http://documentation.magnolia.info/ > > ---------------------------------------------------------------- > > > > > ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
