# ElasticSearch skip results Perfomance

**URL:** https://discuss.elastic.co/t/elasticsearch-skip-results-perfomance/10368
**Category:** Elasticsearch
**Created:** [January 16, 2013, 6:56am UTC](https://discuss.elastic.co/t/elasticsearch-skip-results-perfomance/10368 "2013-01-16T06:56:08Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Alexis\_Okuwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexis_okuwa/32/1983_2.png) [@Alexis\_Okuwa](https://discuss.elastic.co/u/Alexis_Okuwa)
#### Post date: [January 16, 2013, 6:56am UTC](https://discuss.elastic.co/t/elasticsearch-skip-results-perfomance/10368/1 "2013-01-16T06:56:08Z")

</div>

I am thinking about making a type of map reduce project using elastic  
search as a first level of filtering, like most people know when someone  
does map reduce do it across a much larger set of data then they need.  
Because I want it to "scale" I dont want to limit the collecting of the  
data from elasticsearch to go to one node and then be split up to be sent  
to the other nodes. I am thinking about using some sort of skip simular to  
how mysql does Limit 5, 10 What I am aware of is that when a skip takes  
place it needs to first pull the first x number of records and then run for  
the next set meaning that I am going to end up pulling a lot of unneeded  
records, anyway around this in elasticsearch?

--

---

<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:56am UTC](https://discuss.elastic.co/t/elasticsearch-skip-results-perfomance/10368/2 "2017-07-06T02:56:12Z")

</div>


