Optimum value for "max_num_segments"

Hello,

1 will give you the best search times, but it will put the most stress on
your system. So I would use 1, unless I'd be bothered by load.

If you are bothered by load, the best way to find a good trade-off is to
test different values while monitor your system with something like
SPMhttp://sematext.com/spm/elasticsearch-performance-monitoring/
.

Best regards,
Radu

On Wed, Jul 10, 2013 at 8:06 AM, subin ksubins321@gmail.com wrote:

Hi,

I have an ES v0.90.0 running on a single server with 1 shard 0 replica per
index configuration.
What is the optimum value for the old index optimize call:

curl -XPOST 'http://localhost:9200/twitter/_optimize?max_num_segments=*2*'

Should it be 2 or 3? How should it be decided? These are Logstash indexes
and they are rotated
daily. Therefore I plan to run the call once everyday.

Thanks,

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
http://sematext.com/ -- Elasticsearch -- Solr -- Lucene

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.