# Will Elasticsearch run on 0.5gb memory? **URL:** \ **Category:** Elasticsearch\ **Created:** [August 16, 2017, 6:58pm UTC](https://discuss.elastic.co/t/will-elasticsearch-run-on-0-5gb-memory/97309 "2017-08-16T18:58:48Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mortenbock](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mortenbock/32/13062_2.png) [@mortenbock](https://discuss.elastic.co/u/mortenbock)\ **Post date:** [August 16, 2017, 6:58pm UTC](https://discuss.elastic.co/t/will-elasticsearch-run-on-0-5gb-memory/97309/1 "2017-08-16T18:58:48Z")
Hi. I am running a low budget website, that is sitting on a windows VM with 2gb of ram. The current memory footprint of the OS and website in total is around 1.3 gb. The reason I want to use Elasticsearch is to have faster access to products, that currently live in a sql server. There is under 1000 products, so the document count is low, but I might want to do some aggregations for filtering etc. Will elasticsearch work well with around 500mb of ram available? Will it even run? Is there a different product which might be a better fit for a low volume/memory document DB? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 16, 2017, 9:49pm UTC](https://discuss.elastic.co/t/will-elasticsearch-run-on-0-5gb-memory/97309/2 "2017-08-16T21:49:55Z")
It should but it may not be the most efficient compared to something else (sqlite, a DB, even a grep in a file) for that size of data. ---
**Author:** ![poojagupta](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@poojagupta](https://discuss.elastic.co/u/poojagupta)\ **Post date:** [August 17, 2017, 10:03am UTC](https://discuss.elastic.co/t/will-elasticsearch-run-on-0-5gb-memory/97309/3 "2017-08-17T10:03:16Z")
Elasticsearch run on allocated heap size . You can modify it via editing heap size in jvm options parameter mentioned in elasticsearch file located at bin folder of your elasticsearch installation folder. ES\_JAVA\_OPTS="-Xms4000m -Xmx4000m" ./bin/elasticsearch Mention the space which your system can allocate for it. ---
**Author:** ![TimWard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timward/32/19574_2.png) [@TimWard](https://discuss.elastic.co/u/TimWard)\ **Post date:** [August 17, 2017, 10:36am UTC](https://discuss.elastic.co/t/will-elasticsearch-run-on-0-5gb-memory/97309/4 "2017-08-17T10:36:55Z")
I would think that if you're having performance problems with an RDBMS with such a tiny amount of data you're doing something wrong, and my first approach would be to find and fix whatever that "something" is rather than move to a whole new technology stack. ---
**Author:** ![mortenbock](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mortenbock/32/13062_2.png) [@mortenbock](https://discuss.elastic.co/u/mortenbock)\ **Post date:** [August 17, 2017, 10:56am UTC](https://discuss.elastic.co/t/will-elasticsearch-run-on-0-5gb-memory/97309/5 "2017-08-17T10:56:41Z")
Hi Tim The SQL schema is not mine. It's created by the eCommerce platform we are using, which does NHibernate magic. I could of course store my own model in a separate table in SQL, but the SQL Azure instance is not very quick, even for simple queries. That is why I want to bring a fast datastore closer to my application for entities that I am using a lot. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 14, 2017, 10:57am UTC](https://discuss.elastic.co/t/will-elasticsearch-run-on-0-5gb-memory/97309/6 "2017-09-14T10:57:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.