Network drives (windows)
-
Problem: Network drives.
For example, we have network drive - 10Tb
we can't change position of HDD's heads, for reading this file we must read (and download) all bytes from start.
time for reading ~22hrs (1Gb/s)Solution:
Plotter makes 4096 files (split 1 plot by 4096), which contain 64*nonces bytes.
Each plot = one of 4096 scoops
something like
1234567891011121314_0_1000000_1000000#3095miner reads one of that files at new block (scoop defined)
time for reading ~10 sec (1Gb/s)any ideas?
@luxe @haitch @catbref @daWaIlet @Creepsky @IceBurst @Lexicon @crowetic
-
@Blago Yes I had a similar thought when doing Amazon and Google Cloud Mining, would of course need a modified plotter and Miner.
How much work is it?
Rich
-
@Blago said in Network drives (windows):
Problem: Network drives.
For example, we have network drive - 10Tb
we can't change position of HDD's heads, for reading this file we must read (and download) all bytes from start.
time for reading ~22hrs (1Gb/s)Solution:
Plotter makes 4096 files (split 1 plot by 4096), which contain 64*nonces bytes.
Each plot = one of 4096 scoops
something like
1234567891011121314_0_1000000_1000000#3095miner reads one of that files at new block (scoop defined)
time for reading ~10 sec (1Gb/s)any ideas?
@luxe @haitch @catbref @daWaIlet @Creepsky @IceBurst @Lexicon @crowetic
For drives over a lan having large files is not problem over the wan this might work, but amazon will lock your account for usual behaviour
-
@Blago I have run a network miner and it wasn't that slow. How are you repositioning? It shouldnt matter if it's local or network if you do a fileseek to offset X. If you're using a driver level reposition that could be a problem - but I doubt you're doing that.


