# search profile breakdown

**URL:** https://discuss.elastic.co/t/search-profile-breakdown/346041
**Category:** Elasticsearch
**Created:** [October 30, 2023, 2:17pm UTC](https://discuss.elastic.co/t/search-profile-breakdown/346041 "2023-10-30T14:17:59Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![getsolaris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/getsolaris/32/126539_2.png) [@getsolaris](https://discuss.elastic.co/u/getsolaris)
#### Post date: [October 30, 2023, 2:17pm UTC](https://discuss.elastic.co/t/search-profile-breakdown/346041/1 "2023-10-30T14:17:59Z")

</div>

hello,

I'm using Elasticsearch's profile API to try and figure out what's taking so long.

I currently have an index implemented with parent-child modeling.

When I run a `has_child` query, I am getting a high `match` in my analytics.

If I check the official documentation for the Profile API, it says the following about matches.

```auto
Because this two-phase process is only used by a handful of queries, the match statistic is often zero

```

Is the `has_child` query a minority query that qualifies for `match` ?

Also, I was wondering if there is a way to reduce `match`.

Thank you for your answer.

---

<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: [November 27, 2023, 2:18pm UTC](https://discuss.elastic.co/t/search-profile-breakdown/346041/2 "2023-11-27T14:18:22Z")

</div>

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