How can a handful of small nodes completely trash a large array?

The location has been upgraded.

The primary array of a mismatch of disks have been swapped to 8x 18TB Drives.

I’ve used two of the older 16TB drives in RAID 0 (bad!) to host all StorJ nodes. I’ve used 150GB of the SSD caching as a read-only option in front of the StorJ array, which makes everything very snappy and is just the performance I am seeking. The performance on the primary array is terrific as well, but now it won’t interfere with StorJ and vice versa.

This concludes my updates in this thread … until the RAID 0 array of courses burns itself to pieces. I’ll be sure to update this thread with an “we told you so” congratulation lol

3 Likes