# Is it okay to store a large data in ES?

**URL:** <https://discuss.elastic.co/t/is-it-okay-to-store-a-large-data-in-es/7948>\
**Category:** Elasticsearch\
**Created:** [June 2, 2012, 12:27pm UTC](https://discuss.elastic.co/t/is-it-okay-to-store-a-large-data-in-es/7948 "2012-06-02T12:27:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mp2893](https://avatars.discourse-cdn.com/v4/letter/m/d9b06d/32.png) [@mp2893](https://discuss.elastic.co/u/mp2893)\
**Post date:** [June 2, 2012, 12:27pm UTC](https://discuss.elastic.co/t/is-it-okay-to-store-a-large-data-in-es/7948/1 "2012-06-02T12:27:16Z")

</div>

Hi,  
This is a super simple question, but googling has not helped me yet.

Is it ok to store a large chunk of data ES?  
For example, I want to store a whole HTML page under the field name of  
"original\_text".  
(I'm planning to store a news article in its HTML format, which is  
about 100KB.)  
So in the future I can access the HTML document whenever I want.

Is this going to cause any problem for ES?  
Increased latency? Or too much cache usage? Or memory constantly being  
swapped?  
If I choose never to cache the result when I access the HTML document,  
is it going to solve any of the issues I mentioned?  
Any tip would be appreciated.  
Thanks.

Ed

---

<div class="post-metadata">

**Author:** ![Radu\_Gheorghe1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radu_gheorghe1/32/2688_2.png) [@Radu\_Gheorghe1](https://discuss.elastic.co/u/Radu_Gheorghe1)\
**Post date:** [June 5, 2012, 6:21am UTC](https://discuss.elastic.co/t/is-it-okay-to-store-a-large-data-in-es/7948/2 "2012-06-05T06:21:56Z")

</div>

I don't see why that would be an issue. Maybe some actually uses ES in  
this kind of setup and might give you some tips, but it should work.

Swapping should only occur if you allocate more memory to ES than you  
have RAM. And that's not recommended - typically half your RAM should  
go to ES. OS caching should be as busy with large documents as it  
would be with more smaller ones (or even less busy).

As for ES caching, AFAIK this applies only to filters, not queries. So  
it depends on how you search.

On Jun 2, 3:27 pm, mp2893 [mp2...@gmail.com](mailto:mp2...@gmail.com) wrote:

> Hi,  
> This is a super simple question, but googling has not helped me yet.
> 
> Is it ok to store a large chunk of data ES?  
> For example, I want to store a whole HTML page under the field name of  
> "original\_text".  
> (I'm planning to store a news article in its HTML format, which is  
> about 100KB.)  
> So in the future I can access the HTML document whenever I want.
> 
> Is this going to cause any problem for ES?  
> Increased latency? Or too much cache usage? Or memory constantly being  
> swapped?  
> If I choose never to cache the result when I access the HTML document,  
> is it going to solve any of the issues I mentioned?  
> Any tip would be appreciated.  
> Thanks.
> 
> Ed

---

<div class="post-metadata">

**Author:** ![mp2893](https://avatars.discourse-cdn.com/v4/letter/m/d9b06d/32.png) [@mp2893](https://discuss.elastic.co/u/mp2893)\
**Post date:** [June 6, 2012, 3:55am UTC](https://discuss.elastic.co/t/is-it-okay-to-store-a-large-data-in-es/7948/3 "2012-06-06T03:55:15Z")

</div>

Thanks for the info Radu.  
I would proceed with my plan.

If I see any odd behavior in my ES, I'll add another thread here.

Regards,  
Ed

2012/6/5 Radu Gheorghe [radu0gheorghe@gmail.com](mailto:radu0gheorghe@gmail.com)

> I don't see why that would be an issue. Maybe some actually uses ES in  
> this kind of setup and might give you some tips, but it should work.
> 
> Swapping should only occur if you allocate more memory to ES than you  
> have RAM. And that's not recommended - typically half your RAM should  
> go to ES. OS caching should be as busy with large documents as it  
> would be with more smaller ones (or even less busy).
> 
> As for ES caching, AFAIK this applies only to filters, not queries. So  
> it depends on how you search.
> 
> On Jun 2, 3:27 pm, mp2893 [mp2...@gmail.com](mailto:mp2...@gmail.com) wrote:
> 
> > Hi,  
> > This is a super simple question, but googling has not helped me yet.
> > 
> > Is it ok to store a large chunk of data ES?  
> > For example, I want to store a whole HTML page under the field name of  
> > "original\_text".  
> > (I'm planning to store a news article in its HTML format, which is  
> > about 100KB.)  
> > So in the future I can access the HTML document whenever I want.
> > 
> > Is this going to cause any problem for ES?  
> > Increased latency? Or too much cache usage? Or memory constantly being  
> > swapped?  
> > If I choose never to cache the result when I access the HTML document,  
> > is it going to solve any of the issues I mentioned?  
> > Any tip would be appreciated.  
> > Thanks.
> > 
> > Ed

---

<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, 3:25am UTC](https://discuss.elastic.co/t/is-it-okay-to-store-a-large-data-in-es/7948/4 "2017-07-06T03:25:29Z")

</div>

Closed on July 6, 2017, 3:25am UTC


