Hi Sam, I have been in a similar scenario (not recently so my answer could be outdated). As far as I remember caching, at least in that scenario, didn't help so much, probably because the field size.
So we went with the second option: a custom SearchComponent connected with Redis. I'm not aware if such component is available somewhere but, trust me, it's a very easy thing to write. Best, Andrea On Mon, 4 Jun 2018, 20:45 Sambhav Kothari, <samb...@metabrainz.org> wrote: > Hi everyone, > > We at MetaBrainz are trying to scale our solr cloud instance but are > hitting a bottle-neck. > > Each of the documents in our solr index is accompanied by a '_store' field > that store our API compatible response for that document (which is > basically parsed and displayed by our custom response writer). > > The main problem is that this field is very large (It takes upto 60-70% of > our index) and because of this, Solr is struggling to keep up with our > required reqs/s. > > Any ideas on how to improve upon this? > > I have a couple of options in mind - > > 1. Use caches extensively. > 2. Have solr return only a doc id and fetch the response string from a KV > store/fast db. > > About 2 - are there any solr plugins will allow me to do this? > > Thanks, > Sam >
