What's the warmer do?


(Ivan Ji) #1

Hi all,

I am wondering what the warmer do and what the reason is that it can
accelerate the indexing.
Does there exist some caching workflow and what does it put into the cache?

Also, if I execute the same query of the warming query manually, could I
get the same effect of the warmer do?
If not, what's the algorithm of it did to warm up?

Ideas?

Regards,

Uvan

--
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/a68e9ded-3600-4971-b764-d2b0b86f6a08%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Adrien Grand) #2

Hi,

Some data in the index needs to be loaded into memory for fast access to
the index. Since this loading is sometimes lazy, warmers are run just
before a new segment gets published in order to ensure that following
requests won't need to load this data as part of the query execution. The
two main things that warmers load into memory are norms (used for scoring)
and fielddata (used for sorting and facets/aggregations).

However, I don't see any reason why warmers would make indexing faster, I
would expect the opposite.

On Fri, Jan 24, 2014 at 11:06 AM, Ivan Ji hxuanji@gmail.com wrote:

Hi all,

I am wondering what the warmer do and what the reason is that it can
accelerate the indexing.
Does there exist some caching workflow and what does it put into the cache?

Also, if I execute the same query of the warming query manually, could I
get the same effect of the warmer do?
If not, what's the algorithm of it did to warm up?

Ideas?

Regards,

Uvan

--
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/a68e9ded-3600-4971-b764-d2b0b86f6a08%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
Adrien Grand

--
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/CAL6Z4j4na6h5RBjdRQTRjDWAmhbPS9fg0M0bWROzpdSK%3DWngsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Ivan Ji) #3

Hi,

Thanks for the replies. So the warmer load the necessary data for searching
the index. In other word, it has the same effect with manually the warming
query instead of pushing into the warmer, right?

Cheers,

Ivan

Adrien Grand於 2014年1月24日星期五UTC+8下午6時14分26秒寫道:

Hi,

Some data in the index needs to be loaded into memory for fast access to
the index. Since this loading is sometimes lazy, warmers are run just
before a new segment gets published in order to ensure that following
requests won't need to load this data as part of the query execution. The
two main things that warmers load into memory are norms (used for scoring)
and fielddata (used for sorting and facets/aggregations).

However, I don't see any reason why warmers would make indexing faster, I
would expect the opposite.

On Fri, Jan 24, 2014 at 11:06 AM, Ivan Ji <hxu...@gmail.com <javascript:>>wrote:

Hi all,

I am wondering what the warmer do and what the reason is that it can
accelerate the indexing.
Does there exist some caching workflow and what does it put into the
cache?

Also, if I execute the same query of the warming query manually, could I
get the same effect of the warmer do?
If not, what's the algorithm of it did to warm up?

Ideas?

Regards,

Uvan

--
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/a68e9ded-3600-4971-b764-d2b0b86f6a08%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
Adrien Grand

--
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/cd42d6c8-a9c4-4013-ac7f-000f1a15a7b6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Adrien Grand) #4

On Fri, Jan 24, 2014 at 11:22 AM, Ivan Ji hxuanji@gmail.com wrote:

Thanks for the replies. So the warmer load the necessary data for
searching the index. In other word, it has the same effect with manually
the warming query instead of pushing into the warmer, right?

Exactly, but actually the warmer is a bit more efficient since it would
only run the query on the part of the index that has changed, this can be
much faster.

--
Adrien Grand

--
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/CAL6Z4j7VGAsuh5F_bBW0Zwc3K_BFK2tZ9iGjtLvJUAzK7Z8F5A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #5