Poor Success rate on hashstore

[jammerdan]

@Alexey

It is not needed for Storj Select and not needed in most cases for Storj Global.

The question was asked from the SNO perspective as it sounded like we are getting to a point where every ms counts. For SNOs and for customers.

@Alexey

For me it sounds like you want that our devs are implemented a special device (or an ARC cache?).

For me it sounds like everything is already there:

@arrogantrabbit

My next experiment would be to configure that same node as:

PassiveMigrate":true,"WriteToNew":false,"ReadNewFirst":false,"TTLToNew":false

and keep the migrate chore on

with

@EasyRhino

In my docker compose file I tried this line:

  - /<nfsmount>/storj:/app/config       #(the normal data location)
  - /<localdrive>/storj/hashstore:/app/config/storage/hashstore   #(a local drive to fake hashstore)

This effectively tricks storj into using a local drive for the hashstore and only the hashstore, old piecesstore (blobs) stay on the NFS mount

I am just assuming that SSDs will outperform HDDs and will continue to do so. SSD technology will be further developed and improved while HDD technology is performance-wise already stagnant because it is at the end of its lifespan the gap will become even wider.

So for me it sounds natural to think of improvements on storage not only about HDDs but also of ways to make use of the state of the art SSD technology that offers incredible speeds already today and will be provide even more performance in the future.