To be clear, there are no solid and reliable prediction rules for Solr - for the simple reason that there are too many non-linear variables - you need to stand up a "proof of concept" system, load it with representative data and execute representative queries and then measure that system. You can then use those numbers to size your production system.

I don't want to give you the impression that this notion of "predicting" or "calculating" the size of a production Solr system is a viable option. Sure, you can try and maybe you will get lucky and maybe you won't be lucky. Flip a coin. But what sane manager would want to "plan" production based on flipping a coin?

-- Jack Krupansky

-----Original Message----- From: Furkan KAMACI
Sent: Tuesday, April 23, 2013 5:48 AM
To: solr-user@lucene.apache.org
Subject: What to test, calculate, measeure for a pre-production version of SolrCloud?

Hi Folks;

This week we will make a pre-production version of our system. I've been
askng some questions for a time and I gor really good responses from mail
list. At pre-production and test step:

* I want to measure how much RAM I should define for my Solr instances,
* I will try to make some predictions about how much disk space I will need
at production step.
* Maybe I will check my answer for that question: which RAID to use (or not
use) etc.

For that questions I got answers from mail list and I have some
approximations about them. Also I know that it is not easy to answer such
questions and I should test them to get more accurate answers.
My question is that::

What do you suggest me at pre-production and test step?

* i.e. give much more heap size to Solr instances to calculate RAM
* use solrmeter to test qps for your cluster
* use sematext or anything else for performance monitoring etc.

I need some advices what to test, calculate, measeure etc. Also there was a
question about Codahale metrics and Graphite. You can advice something
about that too.

PS: I use Solr 4.2.1 for tests but if Solr 4.3 becomes ready (if it is
tagged at repository) I will use it.

Reply via email to