[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[EP-tech] Re: Antwort: Use of truncation in advanced searches
One thing we did on our platform was the change described here:
https://github.com/eprints/eprints/issues/120 (see also: http://www.eprints.org/tech.php/18677.html).
The description of this issue is around simple searches (when you?re not using Xapian), but I don?t know if it would have any effect on the advanced searches too.
In some circumstances, MySQL takes longer to work out the best way to run a query than it would take just running the query inefficiently. This change makes it try less iterations to find the ?best? way to run the query.
Might be worth a try?
From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of martin.braendle at id.uzh.ch
Sent: 21 April 2015 10:19
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] Antwort: Use of truncation in advanced searches
our repo has about 80'000 records and 56% fulltext, so is comparable to yours.
Advanced search of thermograph* in
title: immediate (1-2 seconds)
documents (full text): 20-30 seconds. The mysql daemon goes up to 70-100% CPU load.
Quick search (Xapian):
title:thermograph* : immediate
thermograph* : immediate
We recommend in our help page (http://www.zora.uzh.ch/help/) that Quick Search should be the tool of choice and only for very precise searches Advanced Search should be used.