Elasricsearch Documentation on Functional Big O Notation

I have often found myself looking into the performance of different
functionality with Elasticsearch. I feel like this is a huge missing piece
of the documentation with ES. The Redis documentation attempts to identify
performance of functionality using Big O Notation or what they refer to as
time complexity.

Is there any sort of documentation like this that I'm missing?

It would be great to have performance details in the documentation with
regards to functionality and design decisions...

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7f4607f8-0f5c-43d4-8500-1bc99fc1a0c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

As with most performance related things in Elasticsearch context, it
depends on too many factors to really provide set figures.

On 28 January 2015 at 11:05, webish gregory@yoursports.com wrote:

I have often found myself looking into the performance of different
functionality with Elasticsearch. I feel like this is a huge missing piece
of the documentation with ES. The Redis documentation attempts to identify
performance of functionality using Big O Notation or what they refer to as
time complexity.

Is there any sort of documentation like this that I'm missing?

It would be great to have performance details in the documentation with
regards to functionality and design decisions...

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/7f4607f8-0f5c-43d4-8500-1bc99fc1a0c1%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/7f4607f8-0f5c-43d4-8500-1bc99fc1a0c1%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_W9JLGa1MNG1-wO1D6mvBSLbwohb2%2Bsb0GkYHv9xjWsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Are there any other best practices like use filter to reduce amount of
document hit?

在 2015年1月28日星期三 UTC+8上午9:04:39,Mark Walkom写道:

As with most performance related things in Elasticsearch context, it
depends on too many factors to really provide set figures.

On 28 January 2015 at 11:05, webish <gre...@yoursports.com <javascript:>>
wrote:

I have often found myself looking into the performance of different
functionality with Elasticsearch. I feel like this is a huge missing piece
of the documentation with ES. The Redis documentation attempts to identify
performance of functionality using Big O Notation or what they refer to as
time complexity.

Is there any sort of documentation like this that I'm missing?

It would be great to have performance details in the documentation with
regards to functionality and design decisions...

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/7f4607f8-0f5c-43d4-8500-1bc99fc1a0c1%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/7f4607f8-0f5c-43d4-8500-1bc99fc1a0c1%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/767b5a74-c406-4780-80e3-173b31f5102c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.