# Help with node optimizations / best practices

**URL:** <https://forum.storj.io/t/help-with-node-optimizations-best-practices/25279>\
**Category:** Node Operators\
**Tags:** windows-gui, proxmox-vm, hardware\
**Created:** [February 20, 2024, 2:10am UTC](https://forum.storj.io/t/help-with-node-optimizations-best-practices/25279 "2024-02-20T02:10:24Z")\
**Posts on this page:** 1\
**Showing post:** 24

<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:** [February 24, 2024, 1:22pm UTC](https://forum.storj.io/t/help-with-node-optimizations-best-practices/25279/24 "2024-02-24T13:22:53Z")

</div>

No. The LVM partition will be slower than a pure ext4. But it has some advantages like an ability to move data from one disk/partition to another or make a parity RAID without a downtime… But it has zero tolerance to bitrot unlike ZFS or BTRFS (in the Synology implementation only though).  
But…

> [@Doh.. Looks like hardware failure coming up!](https://forum.storj.io/t/doh-looks-like-hardware-failure-coming-up/16181/14):
>
> I would not highlight this feature as zfs-only. You can do that on any nowadays FS/LVM which supports RAID. I would say that btrfs is working much faster than zfs and even pure ext4. But their RAID is a mess. And btrfs is still not production-ready. I would strongly recommend to avoid it in the next 5-10 years (accordingly their velocity on fixing a major bugs). I managed to lost data in the test environment on btrfs single during expand, what’s never happened neither with zfs or LVM. I made …

---

_[View the full topic](https://forum.storj.io/t/help-with-node-optimizations-best-practices/25279)._
