clearly sounds like it’s some sort of program cycle, never the less it’s a problem…
the larger the node gets the more activity… is the disk full?
ofc if the disk was full it would slow down a lot in some cases… i believe a regular hdd is about half the speed and iops at the closest part of the spindle (disk)
and since a hdd will normally fill from the fastest to the slowest parts, then when a hdd goes past the 50% mark in capacity one will start to feel a significant decrease in performance…
ofc this might not be what you are seeing, because it sounds very much like a programming thing… however the reason that you haven’t seen it in the past may have been due to the disk being faster when having more capacity free.
what can you do… well if you disk is full or close to being full… just add another node so the load is spread over two disk… having 1 node and 1 hdd running is the max load setup.
storj have been working on getting the nodes to run fine on just 1 disk pr IP
but just adding another node will put you at 2 disk pr IP giving you a 50/50% split in load for in most cases…
its not really a fix, more like a patch that doubles you hdd resources…
i know it’s a very blanket all slight gamble solution… but its easy to spend a lot of time fixing a problem that might not be able to be fixed… this way you progress…
ofc if you got 1tb on the 12tb drive it wouldn’t be my choice, but if you got 8 or 10… then i wouldn’t even think twice before going that route.
anyways i’m sure there are as many ideas as there are people…
oh and non of the images seems to post…
if it’s metadata / garbage collection… some ssd caching might help… if thats an option…