# Impact of schema fields limit on performance

**URL:** <https://discuss.elastic.co/t/impact-of-schema-fields-limit-on-performance/320747>\
**Category:** Elastic Search\
**Tags:** elastic-app-search\
**Created:** [December 8, 2022, 6:33am UTC](https://discuss.elastic.co/t/impact-of-schema-fields-limit-on-performance/320747 "2022-12-08T06:33:57Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Beratna](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Beratna](https://discuss.elastic.co/u/Beratna)\
**Post date:** [December 15, 2022, 11:23pm UTC](https://discuss.elastic.co/t/impact-of-schema-fields-limit-on-performance/320747/3 "2022-12-15T23:23:15Z")

</div>

Thanks for your response Nick!

I was referring to the "app\_search.engine.total\_fields.limit" setting, let me see if I can break it down:

Scenario 1:  
100 fields (stored but not searched)  
10 fields searched and used for relevance tuning  
5 fields returned

Scenario 2:  
800 fields (stored but not searched)  
10 fields searched and used for relevance tuning  
5 fields returned

I think the performance be about the same since I'm searching over the same amount of fields?

> [@64 fields limitation in 7.16.3](https://discuss.elastic.co/t/64-fields-limitation-in-7-16-3/304322):
>
> Hello, How can we increase the Schema Fields limit in 7.16.3 release? Thank You.

I'll try it out! Thanks for the tips, I'll keep them in mind 👍

---

_[View the full topic](https://discuss.elastic.co/t/impact-of-schema-fields-limit-on-performance/320747)._
