# Impact of marvel on performance

**URL:** <https://discuss.elastic.co/t/impact-of-marvel-on-performance/19535>\
**Category:** Elasticsearch\
**Created:** [August 30, 2014, 11:57am UTC](https://discuss.elastic.co/t/impact-of-marvel-on-performance/19535 "2014-08-30T11:57:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deep\_2](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@Deep\_2](https://discuss.elastic.co/u/Deep_2)\
**Post date:** [August 30, 2014, 11:57am UTC](https://discuss.elastic.co/t/impact-of-marvel-on-performance/19535/1 "2014-08-30T11:57:46Z")

</div>

Hi,  
What is the impact of Marvel on elastic search performance. I have a single  
node elastic search deployment and I have installed marvel plugin. It seems  
that marvel also creates indexes on the node.

How big is the marvel index and if the UI queries that index say every 10  
secs will it adversely impact performance of elastic search.

Please guide.

Regards,  
Deep

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2e8fad13-b8b5-4fed-b9a2-037b99a0ebdf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2e8fad13-b8b5-4fed-b9a2-037b99a0ebdf%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\
**Post date:** [August 30, 2014, 6:17pm UTC](https://discuss.elastic.co/t/impact-of-marvel-on-performance/19535/2 "2014-08-30T18:17:18Z")

</div>

The Marvel indices tend to be small (you only have 1 node and I therefore  
assume not too many indices). It will also have a little memory signature,  
if you are using the UI. Marvel creates a new index every day, so will know  
within a day how big it gets for you. You need to decide how many days of  
data you want to keep and delete old ones. Curator  
([GitHub - elastic/curator: Curator: Tending your Elasticsearch indices](http://github.com/elasticsearch/curator) ) is a handy tool for that.

As far as search performance goes - it shouldn't have any serious impact  
and if you don't have the marvel UI open it will have no impact at all.

Cheers,  
Boaz

On Saturday, August 30, 2014 1:57:46 PM UTC+2, Deep wrote:

> Hi,  
> What is the impact of Marvel on Elasticsearch performance. I have a  
> single node Elasticsearch deployment and I have installed marvel plugin.  
> It seems that marvel also creates indexes on the node.
> 
> How big is the marvel index and if the UI queries that index say every 10  
> secs will it adversely impact performance of Elasticsearch.
> 
> Please guide.
> 
> Regards,  
> Deep

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d19b0c97-799a-4189-b3e5-9640cb098401%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d19b0c97-799a-4189-b3e5-9640cb098401%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:05am UTC](https://discuss.elastic.co/t/impact-of-marvel-on-performance/19535/3 "2017-07-06T01:05:21Z")

</div>

Closed on July 6, 2017, 1:05am UTC


