# Recommendation to use search after instead of scrolling

**URL:** <https://discuss.elastic.co/t/recommendation-to-use-search-after-instead-of-scrolling/268293>\
**Category:** Elasticsearch\
**Created:** [March 25, 2021, 6:31am UTC](https://discuss.elastic.co/t/recommendation-to-use-search-after-instead-of-scrolling/268293 "2021-03-25T06:31:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 25, 2021, 9:04am UTC](https://discuss.elastic.co/t/recommendation-to-use-search-after-instead-of-scrolling/268293/4 "2021-03-25T09:04:19Z")

</div>

Please format your code, logs or configuration files using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and **not the citation button**. It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

This is the icon to use if you are not using markdown format:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e6e239431ec2d71cbf1beef741f2e93e7cc762c.jpg)

> [@prelator](#):
>
> scroll: 5,1s  
> search\_after: 49s

That's a huge difference indeed.  
I'd may be try to decrease the `size` for `search_after`. But for your use case anyway, I'd use the scroll API as your goal is to extract everything.

Pinging @jimczi as he might know what is happening.

---

_[View the full topic](https://discuss.elastic.co/t/recommendation-to-use-search-after-instead-of-scrolling/268293)._