# Wastedcspace in big node

**URL:** <https://forum.storj.io/t/wastedcspace-in-big-node/26555>\
**Category:** troubleshooting\
**Tags:** windows-gui\
**Created:** [June 10, 2024, 11:47am UTC](https://forum.storj.io/t/wastedcspace-in-big-node/26555 "2024-06-10T11:47:36Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [June 11, 2024, 6:37am UTC](https://forum.storj.io/t/wastedcspace-in-big-node/26555/6 "2024-06-11T06:37:04Z")

</div>

Ideal is to do not use VMs at all. And not Windows. Also 1 disk/1 node and not all at once, but when the previous almost full or at least vetted.  
However, you are using what you have now.  
If you going to reconfigure, please do not use VM, the performance will be bad especially on NTFS and especially VMWare.  
Use docker instead if the host is Linux. If the host is Windows then docker is not a best option, since it will be in the Linux VM too, but at least you may run several nodes there without much of issues or you may use [Win GUI Storj Node Toolbox](https://forum.storj.io/t/win-gui-storj-node-toolbox/4381) to run several Windows services instead.

---

_[View the full topic](https://forum.storj.io/t/wastedcspace-in-big-node/26555)._