# ERROR: Out of memory with Foundationdb 7.0.0

**URL:** <https://forums.foundationdb.org/t/error-out-of-memory-with-foundationdb-7-0-0/3429>\
**Category:** Using FoundationDB\
**Created:** [July 6, 2022, 8:50am UTC](https://forums.foundationdb.org/t/error-out-of-memory-with-foundationdb-7-0-0/3429 "2022-07-06T08:50:54Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![redcuckoo](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/redcuckoo/32/1660_2.png) [@redcuckoo](https://forums.foundationdb.org/u/redcuckoo)\
**Post date:** [September 22, 2022, 8:50pm UTC](https://forums.foundationdb.org/t/error-out-of-memory-with-foundationdb-7-0-0/3429/8 "2022-09-22T20:50:43Z")

</div>

Following up this issue, as we managed to resolve it.

What helped:

- increasing transaction processes amount at least to the recommend (8), better to set their amount the same as the amount of storage processes (for 12 storage processes - 12 transaction processes)
- giving storage processes more memory, particulary it should be at least 12Gib for our load, perfectly 16Gib
- as a side note, on the servers with not as many memory available, when configuring, transaction processes doesn’t require more than 4-5Gib of RAM configured
- if you have 8Tb and more disks, it’s better to split it up to smaller disks of 4Tb, as mentioned in the documentation

What we tried but didn’t help:

- decreasing load on the foundationdb
- disabling huge pages (offered in one solution here)

---

_[View the full topic](https://forums.foundationdb.org/t/error-out-of-memory-with-foundationdb-7-0-0/3429)._
