# Speed and size difference with "mult-fields, multi-analyzers" Indexing

**URL:** <https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453>\
**Category:** Elasticsearch\
**Created:** [June 5, 2019, 8:52pm UTC](https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453 "2019-06-05T20:52:50Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![hacker\_21](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hacker\_21](https://discuss.elastic.co/u/hacker_21)\
**Post date:** [June 5, 2019, 8:52pm UTC](https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453/1 "2019-06-05T20:52:50Z")

</div>

Hi,

I just reviewed the documentation for the `fields` option:  
`https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html`

I plan on indexing my data with a `snowball analyzer` and also retaining the regular version of a field with a `text` type.

I'm wondering if using this approach would double the size of the index? With the original copy and the "snowball analyzed" copy?

Also, does querying the "fields" or "embedded" version have any significant query time speed slow downs? It reminds me of the nested query, so I'm nervous it might slow down the overall search/query speed.

Thanks!

---

<div class="post-metadata">

**Author:** ![hacker\_21](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hacker\_21](https://discuss.elastic.co/u/hacker_21)\
**Post date:** [June 7, 2019, 3:58am UTC](https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453/2 "2019-06-07T03:58:24Z")

</div>

Any ideas? Hoping someone else has implemented this approach and can share their experience

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 7, 2019, 5:16am UTC](https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453/3 "2019-06-07T05:16:27Z")

</div>

That's probably the right way to solve your use case.

---

<div class="post-metadata">

**Author:** ![gabriel\_tessier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabriel_tessier/32/27911_2.png) [@gabriel\_tessier](https://discuss.elastic.co/u/gabriel_tessier)\
**Post date:** [June 7, 2019, 7:06am UTC](https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453/4 "2019-06-07T07:06:42Z")

</div>

Hi,

I am a heavy user of multi-fields, yes the size of the document increase and it depends on your document, if you have only 1 field and add analyzer to this field there's a chance to double, depends on the result of the analyzer I think...

For speed concern I didn't notice difference. Hope that my post help you to feel less nervous. 😁

Depends on how much documents you have, so better to make some benchmark with your data before.

---

<div class="post-metadata">

**Author:** ![hacker\_21](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hacker\_21](https://discuss.elastic.co/u/hacker_21)\
**Post date:** [June 7, 2019, 6:49pm UTC](https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453/5 "2019-06-07T18:49:59Z")

</div>

Thank you! I'll keep all of it in mind

---

<div class="post-metadata">

**Author:** ![hacker\_21](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hacker\_21](https://discuss.elastic.co/u/hacker_21)\
**Post date:** [June 9, 2019, 4:28am UTC](https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453/6 "2019-06-09T04:28:50Z")

</div>

Just wanted to update. I made 3 of my fields into "multi-fields" with a snowball analyzer and just a regular "text" type copy.

Obviously, your own results are going to be different, but I thought I'd share my stats regardless.

This is a small subset of my data, but here's my dataset stats the old way (all 3 fields only had a snow-ball analyzer ... no text copy):  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/1/d13e3f83763d5a81e2b1941d8d49d143ca76447c.png)

After re-ingesting the data as multifield:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/a/9a53c14534d0888d695ab3d5afc2671b390d14f4.png)  
It was about double after the multifield mapping, which is what I was expecting.

However, after about 15 minutes, the size of the index went down:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/5/a5e67de5ddbeb1f0b44066dbc3613f452a3ee4c2.png)  
Chart confirms it ...  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/0/609a6fe013687fdd0b8b34c5a6819a0ac090711a.png)

nice to see elasticsearch doing its magic! Appears to have taken less than double in my case, which is awesome to see.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 7, 2019, 4:34am UTC](https://discuss.elastic.co/t/speed-and-size-difference-with-mult-fields-multi-analyzers-indexing/184453/7 "2019-07-07T04:34:12Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
