# Geo\_bounding\_box on 10 billion objects

**URL:** <https://discuss.elastic.co/t/geo-bounding-box-on-10-billion-objects/10703>\
**Category:** Elasticsearch\
**Created:** [February 11, 2013, 8:41pm UTC](https://discuss.elastic.co/t/geo-bounding-box-on-10-billion-objects/10703 "2013-02-11T20:41:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mohamed\_Lrhazi](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@Mohamed\_Lrhazi](https://discuss.elastic.co/u/Mohamed_Lrhazi)\
**Post date:** [February 11, 2013, 8:41pm UTC](https://discuss.elastic.co/t/geo-bounding-box-on-10-billion-objects/10703/1 "2013-02-11T20:41:31Z")

</div>

Hello,

How much resources would it take, and what topology/config would I need to  
use, to provide for this, if at all possible:

Index 10 billion simple objects with the following schema, and provide  
subsecond geo\_bounding\_box search:

item:  
location: (lon, lat)  
color: small\_string

I have been doing some tests and I can easily get sub second searches with  
10 million objects (am only interested in the hits number BTW), on single  
instance, 32GB RAM, 2 vCPUs, and elasticsearch started with options -Xmx30g  
-Xms30g

How many nodes, how much RAM each, would you expect to need to reach such a  
goal? What would I need to learn and tweak or change from elasticsearch  
default settings for sharding, indexing and searching?

Or is elasticsearch the wrong tool for such a task? would mongodb be more  
appropriate? given the size of the data set?

Thanks a lot,  
Mohamed.

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [February 12, 2013, 10:52pm UTC](https://discuss.elastic.co/t/geo-bounding-box-on-10-billion-objects/10703/2 "2013-02-12T22:52:15Z")

</div>

Hard to tell on how many nodes you will need to run it. Geo bounding box is CPU heavy, the more nodes you have, the better your search performance will be (and make sure you have enough shards).

Side note: We don't recommend setting the ES\_HEAP\_SIZE to 30gb on a 32gb machine, you want to keep a bit for the OS file system cache. Since geo bounding box requires loading the lat/lon fields to be loaded to memory, you will need memory for it, but I wouldn't pass the 22gb mark on a 32gb box.

On Feb 11, 2013, at 9:41 PM, Mohamed Lrhazi [ml623@georgetown.edu](mailto:ml623@georgetown.edu) wrote:

> Hello,
> 
> How much resources would it take, and what topology/config would I need to use, to provide for this, if at all possible:
> 
> Index 10 billion simple objects with the following schema, and provide subsecond geo\_bounding\_box search:
> 
> item:  
> location: (lon, lat)  
> color: small\_string
> 
> I have been doing some tests and I can easily get sub second searches with 10 million objects (am only interested in the hits number BTW), on single instance, 32GB RAM, 2 vCPUs, and elasticsearch started with options -Xmx30g -Xms30g
> 
> How many nodes, how much RAM each, would you expect to need to reach such a goal? What would I need to learn and tweak or change from elasticsearch default settings for sharding, indexing and searching?
> 
> Or is elasticsearch the wrong tool for such a task? would mongodb be more appropriate? given the size of the data set?
> 
> Thanks a lot,  
> Mohamed.
> 
> --  
> 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).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Mohamed\_Lrhazi](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@Mohamed\_Lrhazi](https://discuss.elastic.co/u/Mohamed_Lrhazi)\
**Post date:** [February 18, 2013, 10:10pm UTC](https://discuss.elastic.co/t/geo-bounding-box-on-10-billion-objects/10703/3 "2013-02-18T22:10:42Z")

</div>

Thanks a lot Kimchy. this might require more nodes than I could afford for  
now 🙂

On Tuesday, February 12, 2013 5:52:15 PM UTC-5, kimchy wrote:

> Hard to tell on how many nodes you will need to run it. Geo bounding box  
> is CPU heavy, the more nodes you have, the better your search performance  
> will be (and make sure you have enough shards).
> 
> Side note: We don't recommend setting the ES\_HEAP\_SIZE to 30gb on a 32gb  
> machine, you want to keep a bit for the OS file system cache. Since geo  
> bounding box requires loading the lat/lon fields to be loaded to memory,  
> you will need memory for it, but I wouldn't pass the 22gb mark on a 32gb  
> box.
> 
> On Feb 11, 2013, at 9:41 PM, Mohamed Lrhazi \<ml...@georgetown.edu\<javascript:\>\>  
> wrote:
> 
> Hello,
> 
> How much resources would it take, and what topology/config would I need to  
> use, to provide for this, if at all possible:
> 
> Index 10 billion simple objects with the following schema, and provide  
> subsecond geo\_bounding\_box search:
> 
> item:  
> location: (lon, lat)  
> color: small\_string
> 
> I have been doing some tests and I can easily get sub second searches with  
> 10 million objects (am only interested in the hits number BTW), on single  
> instance, 32GB RAM, 2 vCPUs, and elasticsearch started with options -Xmx30g  
> -Xms30g
> 
> How many nodes, how much RAM each, would you expect to need to reach such  
> a goal? What would I need to learn and tweak or change from elasticsearch  
> default settings for sharding, indexing and searching?
> 
> Or is elasticsearch the wrong tool for such a task? would mongodb be more  
> appropriate? given the size of the data set?
> 
> Thanks a lot,  
> Mohamed.
> 
> --  
> 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:50am UTC](https://discuss.elastic.co/t/geo-bounding-box-on-10-billion-objects/10703/4 "2017-07-06T02:50:51Z")

</div>

Closed on July 6, 2017, 2:50am UTC


