What he said. But if you must have a number, assume that the index will be as big as your (text) data. It might be 2X bigger or 2X smaller. Or 3X or 4X, but that is a starting point. Once you start updating, the index might get as much as 2X bigger before merges.
Do NOT try to get by with the smallest possible RAM or disk. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Feb 3, 2020, at 5:28 AM, Erick Erickson <erickerick...@gmail.com> wrote: > > I’ve always had trouble with that advice, that RAM size should be JVM + index > size. I’ve seen 300G indexes (as measured by the size of the data/index > directory) run in 128G of memory. > > Here’s the long form: > https://lucidworks.com/post/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/ > > But the short form is “stress test and see”. > > To answer your question, though, when people say “index size” they’re usually > referring to the size on disk as I mentioned above. > > Best, > Erick > >> On Feb 3, 2020, at 4:24 AM, Mohammed Farhan Ejaz <farhan.e...@gmail.com> >> wrote: >> >> Hello All, >> >> I want to size the RAM for my Solr cloud instance. The thumb rule is your >> total RAM size should be = (JVM size + index size) >> >> Now I have a simple question, How do I know my index size? A simple method, >> perhaps from the Solr cloud admin UI or an API? >> >> My assumption so far is the total segment info size is the same as the >> index size. >> >> Thanks & Regards >> Farhan >
