Hi Saurabh, Welcome to the channel! Storing fields should not affect query performances directly if you use lazy field loading and it is the default set. And it should not affect at all if you have enough RAM compared to index size. Otherwise OS caches might be affected by stored fields. The best way to tell is to tests with expected indexing/partial updates load and see if/how much it affects performances.
HTH, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > On 26 Feb 2019, at 09:34, Saurabh Sharma <saurabh.infoe...@gmail.com> wrote: > > Hi All , > > > I am new here on this channel. > Few days back we upgraded our solr cloud to version 7.3 and doing real-time > document posting with 15 seconds soft commit and 2 minutes hard commit > time.As of now we posting full document to solr which includes data > accumulations from various sources. > > Now we want to do partial updates.I went through the documentation and > found that all the fields should be stored or docValues for partial > updates. I have few questions regarding this? > > 1) In case i am just fetching only 1 field while making query.What will the > performance impact due to all fields being stored? Lets say i have an "id" > field and i do have doc value true for the field, will solr use stored > fields in this case? will it load whole document in RAM ? > > 2)What's the impact of large stored fields (.fdt) on query time > performance. Do query time even depend on the stored field or they just > depend on indexes? > > > Thanks and regards > Saurabh
