# Combining fields into one for performance?

**URL:** <https://discuss.elastic.co/t/combining-fields-into-one-for-performance/324433>\
**Category:** Elasticsearch\
**Created:** [February 1, 2023, 1:59pm UTC](https://discuss.elastic.co/t/combining-fields-into-one-for-performance/324433 "2023-02-01T13:59:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryans](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@ryans](https://discuss.elastic.co/u/ryans)\
**Post date:** [February 1, 2023, 1:59pm UTC](https://discuss.elastic.co/t/combining-fields-into-one-for-performance/324433/1 "2023-02-01T13:59:10Z")

</div>

I currently have 140 fields in my Elasticsearch index-based App Search Engine. I realized that 40 of those fields contain data that does not need to be indexed (it's display only data), so I marked them index:false in the mapping. After thinking about it, I could combine those 40 fields into one called "display\_only\_data" or similar with the idea that reducing the number of fields by 40 will help the system perform better.

So my questions are:

1. Does reducing the number of fields help the system perform better?
2. If fields are marked index:false, do they not impact the system - meaning they don't really count towards the number of fields because they are not indexed anyway?

Thanks in advance!

---

<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:** [March 1, 2023, 1:59pm UTC](https://discuss.elastic.co/t/combining-fields-into-one-for-performance/324433/2 "2023-03-01T13:59:47Z")

</div>

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