# Indexing a string property is taking several days and it doesn't seem near to completion

**URL:** <https://community.neo4j.com/t/indexing-a-string-property-is-taking-several-days-and-it-doesnt-seem-near-to-completion/6696>\
**Category:** Operations\
**Tags:** index\
**Created:** [April 18, 2019, 7:15am UTC](https://community.neo4j.com/t/indexing-a-string-property-is-taking-several-days-and-it-doesnt-seem-near-to-completion/6696 "2019-04-18T07:15:03Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![dsolow](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/dsolow/32/4431_2.png) [@dsolow](https://community.neo4j.com/u/dsolow)\
**Post date:** [June 27, 2019, 11:55pm UTC](https://community.neo4j.com/t/indexing-a-string-property-is-taking-several-days-and-it-doesnt-seem-near-to-completion/6696/8 "2019-06-27T23:55:22Z")

</div>

Hi Michael. I'm running into a similar problem where my index building is taking a prohibitively long time (~7 hours to index a node property on 200M nodes). I've tried using this `blockBasedPopulation` but building the index with this setting enabled causes an out of memory crash. The index builds for a while (around an hour) with low memory usage. Then memory usage spikes, and the DB gets OOM-killed.

Any ideas on how this could be resolved? I'm using 3.5.6

---

_[View the full topic](https://community.neo4j.com/t/indexing-a-string-property-is-taking-several-days-and-it-doesnt-seem-near-to-completion/6696)._
