Does Up Load and Down Load speed factor in??
My current Up load and Down load is 22 ms ping
33.42 Mbps these numbers are from speedtest on line. Does this effect anything in the mining process???
Luke1219 last edited by
Nope, my internet is less than that, and my mining is fine unless it cuts off
@Luke1219 ok cool so mining revolves around the amount of TB you have more than anything else.
@croydan1 How fast you read the files also helps too. Latency between your Server can be an issue if it is a very fast block. Or if it is a fast round your shares won't make it in time. But anything under 1 minute scan of the drives is decent but most small rigs should be under 30 seconds to read.
@CryptoNick my read times right now are 02:36:34 Thread "F:\Burst\plots" @ 5.6 sec (40.5 MB/s) CPU 37.96%
02:36:34 Thread "E:\Burst\plots" @ 5.7 sec (43.0 MB/s) CPU 40.06%
02:36:35 Thread "D:\Burst\plots" @ 6.3 sec (56.5 MB/s) CPU 50.83%
02:36:44 [ 9611890149370107819] confirmed DL: 226126 2d 14:48:46
02:36:54 New block 314796, baseTarget 1446495, netDiff 12668 Tb
02:36:54 [ 9611890149370107819] found DL: 2697156
02:36:54 [ 9611890149370107819] sent DL: 2697156 31d 05:12:36
02:36:55 [ 9611890149370107819] found DL: 2235173
02:36:55 [ 9611890149370107819] sent DL: 2235173 25d 20:52:53
02:36:56 [ 9611890149370107819] found DL: 521528
02:36:56 [ 9611890149370107819] sent DL: 521528 6d 00:52:08
02:36:59 Thread "F:\Burst\plots" @ 5.6 sec (40.7 MB/s) CPU 37.35%
02:36:59 Thread "E:\Burst\plots" @ 5.8 sec (42.7 MB/s) CPU 39.14%
02:37:00 Thread "D:\Burst\plots" @ 6.3 sec (56.5 MB/s) CPU 50.69%
02:37:07 [ 9611890149370107819] confirmed DL: 2697156 31d 05:12:36 I really hope i am reading things correctly
02:37:11 New block 314797, baseTarget 1384831, netDiff 13232 Tb
02:37:12 [ 9611890149370107819] found DL: 2698578
02:37:12 [ 9611890149370107819] sent DL: 2698578 31d 05:36:18
02:37:14 [ 9611890149370107819] found DL: 70562
02:37:14 [ 9611890149370107819] sent DL: 70562 0d 19:36:02
02:37:16 Thread "F:\Burst\plots" @ 5.2 sec (43.4 MB/s) CPU 38.27%
02:37:16 Thread "E:\Burst\plots" @ 5.6 sec (44.4 MB/s) CPU 38.72%
02:37:17 Thread "D:\Burst\plots" @ 6.1 sec (58.2 MB/s) CPU 49.60%
02:37:21 [ 9611890149370107819] confirmed DL: 2698578 31d 05:36:18
02:37:41 [ 9611890149370107819] confirmed DL: 70562 0d 19:36:02
100 3312 136.05 Mb/s). Deadli
@croydan1 are these good read times its a total of 3.2TB?????
@croydan1 Perfect times should be fine!
@CryptoNick great so not to be a pain but how do I get the DL times faster so i'm more consistent in shorter time span?????
@croydan1 The Drives will read their capacity only so fast everytime. You can Optimize them to squeak out a little more time but 5 seconds is good. It is only when you have more drives that you may need to do anything.
Getting lower Deadlines is a matter of Luck and Size of your plots. So you will need more capacity to have better luck and more chances for lower Deadlines.
@CryptoNick that is good to know if I am understanding this correctly the larger the HD meaning and im going to talk crazy for a sec if I bought a single 8TB HD then I could in effect shorten the DL time?
@croydan1 I want to tell you I am very great full for the advice and your time!
@croydan1 Happy to help! And you won't lose any rounds with those times either. If the Deadline is there in your Plot you are going to get it if no one beats the time.
Example: you find a 1:30 Deadline in 6 Seconds of read time. You have to wait 1:30 and other miners are submitting still. Many of the miners take 1 Minute just to read their larger plots. So if you luck out and no deadline beats your 1:30 your pool will share the coin and you will get the majority percentage. The other miners could find a 10 second Deadline though at 1:00 that stops the round immediately.
@CryptoNick ok now it is making more sense nice and as of now i finally am up to 5TB sloooowwwwly building woohoo.