# Import Script High Memory Usage

**URL:** <https://meta.discourse.org/t/import-script-high-memory-usage/153471>\
**Category:** Product Support\
**Created:** [June 1, 2020, 2:04pm UTC](https://meta.discourse.org/t/import-script-high-memory-usage/153471 "2020-06-01T14:04:30Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Ghan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ghan/32/177964_2.png) [@Ghan](https://meta.discourse.org/u/Ghan)\
**Post date:** [June 1, 2020, 2:35pm UTC](https://meta.discourse.org/t/import-script-high-memory-usage/153471/5 "2020-06-01T14:35:28Z")

</div>

> [@pfaffman](#):
>
> Did you look at the bulk import scripts?

I’m not aware of any bulk import scripts. Are these in the import\_scripts directory somewhere?

> [@pfaffman](#):
>
> You understand that after you run the initial import you’ll run it again to import just the new data and it’ll run much faster, right?

Yes, this is where I’m having trouble. Things were comparatively fine during the initial import running 8 import processes, up until the system ran out of memory. Now when I attempt to restart the import process and pick up where it left off, each process is using about 5 times the memory that it was when it crashed the first time.

We need to get a full import complete to have a proper test and set expectations for when this migration may happen for real. Right now I still don’t have a clear understanding of what to expect regarding things like performance. And I’ve also noticed that even at the 16 million post mark, the database size is already over 50% larger than our current database - that is a bit of a surprise. The long import time doesn’t make this impossible to do, but it would certainly be much more convenient if the expectation was framed in days instead of weeks.

---

_[View the full topic](https://meta.discourse.org/t/import-script-high-memory-usage/153471)._