I knew facet building could slow down opac and staff search, but I did not make tests before... If I suppress all the facet building code in Search.pm, opac results take 2 seconds to show up on a big search (>5000 results) Without any code suppression, and maxRecordsForFacets=4000, it takes 7-8 seconds With maxRecordsForFacets=2000, 4-5 seconds With maxRecordsForFacets=1000, 3-4 seconds With maxRecordsForFacets=500, 2-3 seconds. So 500 is maybe a good value for some libraries (I tested with a small virtual machine) M. Saby Nicole Engard a écrit :
On Mon, Nov 19, 2012 at 10:54 AM, Mathieu Saby <mathieu.saby@univ-rennes2.fr <mailto:mathieu.saby@univ-rennes2.fr>> wrote:
maybe for some (not all...) libraries it could be good to sort facets results by decreasing occurences order. Would you agree a syspref for that ?
Yes if you change sorting it should be controlled by a preference because even though we have a preference to show facets based on more results it's not feasible for most libraries because it slows things down way too much.
Nicole
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr