Loading from _source, especially in scripts, is slow, and uses additional memory. Also note that large _source field is compressed, which adds another bit of CPU overhead.
With stored fields, you have finer control over these issues. So it might make sense to compress large binary data fields http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#binary Jörg On Mon, Sep 22, 2014 at 3:41 PM, Nikolas Everett <[email protected]> wrote: > My understanding is that it is mostly more efficient to not store any > fields and just let Elasticsearch load them from the source when needed. > > Nik > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1jz8QDjd074xhJm2bDetVH4svzSbWc7970oCYWQw6wOg%40mail.gmail.com > <https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1jz8QDjd074xhJm2bDetVH4svzSbWc7970oCYWQw6wOg%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG5oynqESWuK3DvsFsebhpqb_jj2uF0o4_GUqKEhuQBVA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
