# How can I speed up tokenizing in elasticsearch?

**URL:** https://discuss.elastic.co/t/how-can-i-speed-up-tokenizing-in-elasticsearch/383141
**Category:** Elasticsearch
**Created:** [November 1, 2025, 9:10am UTC](https://discuss.elastic.co/t/how-can-i-speed-up-tokenizing-in-elasticsearch/383141 "2025-11-01T09:10:48Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![orlenkoda5](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/orlenkoda5/32/117648_2.png) [@orlenkoda5](https://discuss.elastic.co/u/orlenkoda5)
#### Post date: [November 1, 2025, 9:10am UTC](https://discuss.elastic.co/t/how-can-i-speed-up-tokenizing-in-elasticsearch/383141/1 "2025-11-01T09:10:48Z")

</div>

I use elasticsearch in social network product to receive and search documents (posts) created by users but there is a problem with searching just created document, it appears in search results after a while (1-2 minutes). It is too slow for us. Can you, please, tell how can we search for a just created document faster?

---

<div class="post-metadata">

### Author: ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)
#### Post date: [November 1, 2025, 9:36am UTC](https://discuss.elastic.co/t/how-can-i-speed-up-tokenizing-in-elasticsearch/383141/2 "2025-11-01T09:36:00Z")

</div>

What’s your refresh\_interval ?

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [November 1, 2025, 10:01am UTC](https://discuss.elastic.co/t/how-can-i-speed-up-tokenizing-in-elasticsearch/383141/3 "2025-11-01T10:01:10Z")

</div>

Apart from the refresh interval, which could on its own explain the delay, it would be useful if you also could provide details about the following:

- Which Elasticsearch version are you using?
- What is the size and mapping complexity of your documents?
- Are you using nested documents, vectors, parent-child or any other featiures that may affect performance?
- What is the size of your data in terms of document count, size on disk and shard count?
- What is the size and specification of your cluster? What type of storage are you using?
- What load is the cluster typically under?
