# Impact of schema fields limit on performance **URL:** \ **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:** 4\ **Page:** 1
**Author:** ![Beratna](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Beratna](https://discuss.elastic.co/u/Beratna)\ **Post date:** [December 8, 2022, 6:33am UTC](https://discuss.elastic.co/t/impact-of-schema-fields-limit-on-performance/320747/1 "2022-12-08T06:33:57Z")
Hi there, I'm currently using App Search with search-ui react library. I was wondering about the search performance impact of increasing the schema fields limit (for ex. 70 vs 100 fields -- only 10 fields are used for relevance tuning in both cases). Will there be a noticeable difference in search response times or will it be negligible if I maintain the same fields for relevance tuning? Thanks! ---
**Author:** ![nickchow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickchow/32/42547_2.png) [@nickchow](https://discuss.elastic.co/u/nickchow)\ **Post date:** [December 15, 2022, 12:11am UTC](https://discuss.elastic.co/t/impact-of-schema-fields-limit-on-performance/320747/2 "2022-12-15T00:11:40Z")
Thanks for your question! Do you mean that you're only searching over 10 fields, and returning an additional 30, or that you search over 70-100 fields but only 10 have a specific relevance tuning? If it's the first case, the performance impact should be negligible. If it's the latter, it will really depend. Here are a few things that can impact performance: - The shape of the data (e.g. the size of the fields and values) - What sort of search you're performing (e.g. if you're faceting over some high-cardinality fields) - The type of response you want (e.g. if you want highlighting enabled for all those fields) – [relevance settings](https://www.elastic.co/guide/en/app-search/current/result-settings-guide.html) should help here. But ultimately the best way to check would be to just try it out! Hope that helps – please let us know if you have any follow up questions. Nick ---
**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")
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 👍 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 12, 2023, 11:23pm UTC](https://discuss.elastic.co/t/impact-of-schema-fields-limit-on-performance/320747/4 "2023-01-12T23:23:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.