# Facets Optimization Question

**URL:** <https://discuss.elastic.co/t/facets-optimization-question/14444>\
**Category:** Elasticsearch\
**Created:** [November 18, 2013, 8:47am UTC](https://discuss.elastic.co/t/facets-optimization-question/14444 "2013-11-18T08:47:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![spancer\_ray](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spancer_ray/32/76303_2.png) [@spancer\_ray](https://discuss.elastic.co/u/spancer_ray)\
**Post date:** [November 18, 2013, 8:47am UTC](https://discuss.elastic.co/t/facets-optimization-question/14444/1 "2013-11-18T08:47:43Z")

</div>

Hi All,

I've got 10 fields doing facet. Faceting those 10 fields in a single request/query is really slow.  
Is there any way to optimize the facet speed? Or should I compose a multi search with 10 requests faceting  
every field per request?

Any suggestions would be great appreciated.  
Spancer

---

<div class="post-metadata">

**Author:** ![spancer\_ray](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spancer_ray/32/76303_2.png) [@spancer\_ray](https://discuss.elastic.co/u/spancer_ray)\
**Post date:** [November 18, 2013, 8:56am UTC](https://discuss.elastic.co/t/facets-optimization-question/14444/2 "2013-11-18T08:56:18Z")

</div>

Now, in my application, I'm using ajax to request those slow faceting fields (e.g. username, org ) which can be secodly loaded in my page. Those int type fields (facet these fields are faster) have been included in the query logic which immediately display in the page with the search hits. But I don't think it's really good idea,  
just for some backup...  
Hope anyway can help.

Thanks a ton,  
Spancer

---

<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 6, 2017, 2:06am UTC](https://discuss.elastic.co/t/facets-optimization-question/14444/3 "2017-07-06T02:06:30Z")

</div>

Closed on July 6, 2017, 2:06am UTC


