# Difference in performance between using metric path parameter and filter\_path query parameter in note stats

**URL:** <https://discuss.elastic.co/t/difference-in-performance-between-using-metric-path-parameter-and-filter-path-query-parameter-in-note-stats/229941>\
**Category:** Elasticsearch\
**Created:** [April 27, 2020, 10:29am UTC](https://discuss.elastic.co/t/difference-in-performance-between-using-metric-path-parameter-and-filter-path-query-parameter-in-note-stats/229941 "2020-04-27T10:29:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![harskum](https://avatars.discourse-cdn.com/v4/letter/h/d78d45/32.png) [@harskum](https://discuss.elastic.co/u/harskum)\
**Post date:** [April 27, 2020, 10:29am UTC](https://discuss.elastic.co/t/difference-in-performance-between-using-metric-path-parameter-and-filter-path-query-parameter-in-note-stats/229941/1 "2020-04-27T10:29:38Z")

</div>

How is the computation of a query done. So, for example if I specify a metric path parameter in `GET _nodes/stats/<metric>` api, are the computations being done for metrics that I passed, or whether it's just another filter in response like the `filter_path` query parameter. I guess what I wanna ask is suppose I use `GET _nodes/stats/<metric>` and `GET _nodes/stats?filter_path=<field1>,<field2>,<field3>` to get a response, and if the size of the response is equal in both cases, which api call would be more performant?

---

<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:** [May 25, 2020, 10:29am UTC](https://discuss.elastic.co/t/difference-in-performance-between-using-metric-path-parameter-and-filter-path-query-parameter-in-note-stats/229941/2 "2020-05-25T10:29:45Z")

</div>

Closed on May 25, 2020, 10:29am UTC

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