# Design draft: a low I/O piece storage

**URL:** <https://forum.storj.io/t/design-draft-a-low-i-o-piece-storage/24864>\
**Category:** Product Discussions\
**Created:** [January 7, 2024, 7:19pm UTC](https://forum.storj.io/t/design-draft-a-low-i-o-piece-storage/24864 "2024-01-07T19:19:38Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [January 8, 2024, 3:56am UTC](https://forum.storj.io/t/design-draft-a-low-i-o-piece-storage/24864/12 "2024-01-08T03:56:02Z")

</div>

Perhaps the most efficient storage was based on LevelDB in Storj v2 ([Introducing KFS: a local file store inspired by Kademlia](https://www.storj.io/blog/introducing-kfs-a-local-file-store-inspired-by-kademlia)), but it has had a hard limit of max allocated size per node, and since it was a custom solution, the repair tools for LevelDB didn’t work well. It also used more memory to operate a node (exactly like you suggests) and we have had many complains about high memory usage.

---

_[View the full topic](https://forum.storj.io/t/design-draft-a-low-i-o-piece-storage/24864)._