Hi Matteo, as an addition to Upayavira observation, how is the memory assigned for that Solr Instance ? How much memory is assigned to Solr and how much left for the OS ? Is this a VM on top of a physical machine ? So it is the real physical memory used, or swapping could happen frequently ? Is there enough memory to allow the OS to cache the stored content index segments in memory ? As a first thing I would try to exclude I/O bottlenecks with the disk ( and apparently your document cache experiment should exclude them) Unfortunately the export request handler is not an option with 4.0 .
Are you obtaining those timings in high load ( huge query load) or in low load timeframes ? What happens if you take the solr instance all for you an repeat the experiment? In an healthy memory mapped scenario i would not expect to half the time of a single query thanks to the document cache ( of course I would expect a benefit but it looks too much difference for something that should be already in RAM). In a dedicated instance , have you tried without the document cache, to repeat the query execution ? ( to trigger possibly memory mapping) But also that should be an alarming point, in a low load Solr, with the document fields in cache ( so java heap memory), it is impressive we take 14s to load the documents fields. I am curious to know updates on this, Cheers On 11 February 2016 at 12:45, Matteo Grolla <matteo.gro...@gmail.com> wrote: > Thanks Toke, yes, they are long times, and solr qtime (to execute the > query) is a fraction of a second. > The response in javabin format is around 300k. > Currently I can't limit the rows requested or the fields requested, those > are fixed for me. > > 2016-02-11 13:14 GMT+01:00 Toke Eskildsen <t...@statsbiblioteket.dk>: > > > On Thu, 2016-02-11 at 11:53 +0100, Matteo Grolla wrote: > > > I'm working with solr 4.0, sorting on score (default). > > > I tried setting the document cache size to 2048, so all docs of a > single > > > request fit (2 requests fit actually) > > > If I execute a query the first time it takes 24s > > > I reexecute it, with all docs in the documentCache and it takes 15s > > > execute it with rows = 400 and it takes 3s > > > > Those are very long execution times. It sounds like you either have very > > complex queries or very large fields, as Binoy suggests. Can you provide > > us with a full sample request and tell us how large a single documnent > > is when returned? If you do not need all the fields in the returned > > documents, you should limit them with the fl-parameter. > > > > - Toke Eskildsen, State and University Library, Denmark > > > > > > > -- -------------------------- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
