# How many users can access Elasticsearch and Kibana at the same time?

**URL:** <https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [January 4, 2024, 2:49pm UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392 "2024-01-04T14:49:31Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![stramzik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stramzik/32/112158_2.png) [@stramzik](https://discuss.elastic.co/u/stramzik)\
**Post date:** [January 4, 2024, 2:49pm UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/1 "2024-01-04T14:49:31Z")

</div>

Hi,

I am running a Elasticsearch and Kibana(V8.10) instance on a single windows server which has 8vCPU and 32gb of RAM.

I would like to get a rough idea on how much load can the Elastic and Kibana instance can handle at a time. The usage would be fairly simple multiple users accessing the dashboards which is created on an index with 400k documents roughly 300mb of data.

I understand it completely depends on the queries and the complexities of the query to elastic based on what i've read on the forum. I would just like to have an estimate of how many users can comfortably access the dashboards with very minimal visualization load.

Could you please advise on what Rally metric should I look at in order to get this figure? i'm very new to this. if you could please point me to any instructions on how to do this, i would be of really great help thank you.

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [January 4, 2024, 6:57pm UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/2 "2024-01-04T18:57:35Z")

</div>

There is no hard limit that I know. but 400k document and 300mb is nothing for elasticsearch which handles millions of documents and displays properly.

I have dev instance which has Millions of document in index but I have not hit any snag on it. But my instance is Linux just FYI.

---

<div class="post-metadata">

**Author:** ![stramzik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stramzik/32/112158_2.png) [@stramzik](https://discuss.elastic.co/u/stramzik)\
**Post date:** [January 5, 2024, 10:36am UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/3 "2024-01-05T10:36:55Z")

</div>

Thank you for your response Sachin!

Have you by any chance ran Rally and performed any sort of test on how many Clients can access your instance at the same time? or do you have a rough ball park figure?

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [January 5, 2024, 9:12pm UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/4 "2024-01-05T21:12:25Z")

</div>

I don't have Rally installed and checking regularly. But I get about 50 user connecting on/off and no problem.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 6, 2024, 12:58am UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/5 "2024-01-06T00:58:25Z")

</div>

Hi @stramzik Let's turn this around a bit 🙂

How many users do you expect?

How Many users do you expect concurrently?

What type of queries / dashboards will they be doing...

Simple Filters? Simple Text? Aggregations?

Did you put Kibana on the Same Server as Elasticsearch?

What else is running on that server?

BTW Rally benchmarks Elasticsearch not Kibana.

---

<div class="post-metadata">

**Author:** ![stramzik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stramzik/32/112158_2.png) [@stramzik](https://discuss.elastic.co/u/stramzik)\
**Post date:** [January 8, 2024, 10:09am UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/6 "2024-01-08T10:09:20Z")

</div>

Thank you Sachin

---

<div class="post-metadata">

**Author:** ![stramzik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stramzik/32/112158_2.png) [@stramzik](https://discuss.elastic.co/u/stramzik)\
**Post date:** [January 8, 2024, 11:38am UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/7 "2024-01-08T11:38:57Z")

</div>

Hi @stephenb

How many users do you expect?  
_ **Around 50-100** _

How Many users do you expect concurrently?  
_ **Probably 15-20** _

What type of queries / dashboards will they be doing...  
Simple Filters? Simple Text? Aggregations?  
_ **Simple filters nothing complex** _

Did you put Kibana on the Same Server as Elasticsearch?  
_ **Yes, Both** _

What else is running on that server?  
_ **Nothing** _

BTW Rally benchmarks Elasticsearch not Kibana.  
_ **I see, so is there a way to really get a number on how many users can access the Kibana platform for the above usage mentioned?** _

---

<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:** [January 8, 2024, 11:50am UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/8 "2024-01-08T11:50:45Z")

</div>

> [@stramzik](#):
>
> The usage would be fairly simple multiple users accessing the dashboards which is created on an index with 400k documents roughly 300mb of data.

That is very little data, so I hope you have created the index with a single primary shard.

You have enoughmemory for a large heap and enough left over for the entire index to fit in the operating system page cache. This is ideal for supporting high levels of query concurrency as you will not be limited by disk I/O as the data fits in memory.

If you have simple and not overly large dashboards I would expect the hardware you have in place to easily support the number of users you mentioned.

---

<div class="post-metadata">

**Author:** ![stramzik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stramzik/32/112158_2.png) [@stramzik](https://discuss.elastic.co/u/stramzik)\
**Post date:** [January 8, 2024, 1:55pm UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/9 "2024-01-08T13:55:27Z")

</div>

Yes, The index is on single primary shard.

Understood, Thank you for the explanation.

---

<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:** [February 5, 2024, 1:56pm UTC](https://discuss.elastic.co/t/how-many-users-can-access-elasticsearch-and-kibana-at-the-same-time/350392/10 "2024-02-05T13:56:17Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
