Advice on how to improve Deadlines



  • Hello, thank you for reading into my post, your suggestions and advice are welcomed!.

    Like everyone here I'm looking for advice about how to improve deadlines.

    I been mining for some time now, so far the best advice to improve deadlines is to increase your plot size, so I started and invested into a 64TB plot and then, documented my results and then augmented my plot to 140TB expecting my ROI to improve....

    As I switched to another pool pool.poolofd32th.club with 30 day minimum deadlines, I found out other people with half the size my plot size were submitting incredibly short and fast deadlines like less than 24 hours consistently and deadlines of less than 8 hours very frequently, so what's going on???

    So while my plot size is 140TB and my deadlines are between 10 days to sometimes when lucky under 24 hours, other miners on the same pool are consistently submitting deadlines under 8 hours with 64TB or smaller plot sizes!!!

    My plot size is at the moment 140TB, I use half on my plot on dedicated internal SATA3 mapping 1 x 8TB SATA3 drive to 1 dedicated SATA port, and the other half of the plot on external dedicated USB3 ports mapping 1 x 8TB drive to 1 dedicated USB3 port.

    I'm GPU mining with jMiner, CPU, GPU and Memory are not saturated, and yes my plots are optimized and not overlapping, jminer goes completely over the 140TB in about 25 second, here is a capture for reference.

    Before I start investing into additional equipment, and optimizing I would like to understand more why miners with smaller plot sizes are submitting to the pool with better deadlines.

    START block '455443', scoopNumber '3483', capacity '140017 GB'
    targetDeadline '2592000', baseTarget '79991', genSig '5fe847..'
    dl '167177368' > '2592000' skipped
    1% done (1TB 0GB), avg.'58 MB/s'
    dl '112714015' > '2592000' skipped
    dl '27271789' > '2592000' skipped
    dl '3481465' > '2592000' skipped
    dl '527733' send (pool) [nonce '248235091']
    26% done (36TB 4GB), avg.'951 MB/s', eff.'1692 MB/s'
    dl '527733' confirmed! [ 6d 2h 35m 33s ]
    dl '508312' send (pool) [nonce '523133176']
    dl '508312' confirmed! [ 5d 21h 11m 52s ]
    51% done (71TB 8GB), avg.'1276 MB/s', eff.'1968 MB/s'
    76% done (106TB 12GB), avg.'1407 MB/s', eff.'1775 MB/s'
    100% done (140TB 17GB), avg.'1347 MB/s', eff.'1190 MB/s'
    FINISH block '455443', best deadline '508312', round time '25s 370ms'

    I mean look at the size of these miners, some of them are not even using plot sizes of over 40TB! what's their secret?

    阔尔吉UP 35.5TB 6.189% 28.10 309U + 8266
    Gallon.He.China 59.0TB 4.679% 21.24 113D + 36449
    ----★-★-★BOOTY BURSTER-★-★-★---- 63.2TB 4.520% 20.52 35D + 1916
    Flying Sky 152.6TB 4.055% 18.41 121D + 4068
    LamHDD6T_0971108558 81.8TB 3.462% 15.72 227D + 208304
    欧阳.China 40.8TB 3.284% 14.91 174D + 248950
    DC29-L5H4-QK9W-EMTLH 41.5TB 2.328% 10.57 156D + 0
    Thread 50.4TB 2.216% 10.06 36D + 15150
    Monster Miner 25.7TB 2.068% 9.39 84D + 27767
    haozhu 43.5TB 1.938% 8.80 180D + 6246
    drjeanjean wallet 11.2TB 1.915% 8.69 7D + 6385
    WITT-BURST 37.8TB 1.863% 8.46 36D + 1863


  • admin

    @sgabay242

    1. Difficulty is bouncing all over the place at the moment, so it's not reliable to compare capacity X today and Capacity Y yesterday. The comparison will vary by hour - you need to look at long term averages,

    1B) The capacity reported by the pool will often be the capacity of one of the miners - the pools generally do not aggregate. eg. I have 10 Miners with 10TB each - total capacity 100TB, but the pool only reports the capacity of one of my miners: 10TB. It's reporting incorrectly by 10x.

    I personally have a 100TB plot spread over three rigs, it often reported as the size of the smallest miner - 7.8TB



  • @haitch thank you for replying, in your opinion how big a plot has to be to submit deadlines under 8 hours pretty consistently? some of these guys are making a killing daily just on snatching slow miners shares and they are not even winning the block in question!



  • @sgabay242 How much on average are you earning / Day /Week?
    How often do you mine a Block on Average?

    Rich



  • @richbc Hey Rich, the answer varies and it depends on the pool conditions, when I first started with "training wheels" I was at pool burst.btfg.space, best day I made 203 burst coins that was with 64TB plot, then when my plot size increased to 140TB and I was getting deadlines under 30 days on every round I switched to pool.poolofd32th.club.
    That's when I realized people with smaller plots than mine were getting deadlines of 8 hours or less, so what's their trick?



  • So how big should a plot size be to generate 8 hour deadlines? 1PB? 2PB? 10PB? does the bus connectivity from SATA/USB and plot size read speed per round has anything to do with achieving better deadlines? I know it helps to rank better at your pool over slow miners, but does it help with your own overall resulting deadlines?

    The other interesting discovery is while my plot is read 140TB @ 25/s I'm looking at the pool.poolofd32th.club screen in real-time and I see people finishing submitting their deadlines for the same round in like 1 or 2 seconds, how is this possible???? I wonder if is WAN network latency involved here, and some of this miners are very close to the pool server, say ASIA, and I'm very far AMERICA?

    As an experiment, I'm looking to convert my miner to Ubuntu and use GPU CreepMiner written in C++, in theory Linux can proceses threads faster than Windows and C++ is Faster than Java (jMiner)



  • @sgabay242 OK here are my thoughts. 🙂

    25 Seconds for 140TB is a very good time and there will be very little if anything to be gained by spending money reducing this, either in hardware or by Changing your Miner.

    For comparison my system which currently has 75TB scans in 12 Seconds, also using jminer. Drives are 4 & 5 TB USB3 each with it's own full speed interface to the Bus.

    I think the only variable you can play with, other than increasing your TB, that might improve your return is the Pool you are mining on.

    Again for comparison looking at the last couple of Weeks (results are now worse than a month ago). I would say that on average on a Day when I do not hit a Block I will earn 80 Burst, was about 100 Burst. On top of that I have hit 8 Blocks in the last Month so an average of about 2 a Week, with an average reward of around 800 Burst, but vary's a lot.

    All these figures very approximate. I have not added them up just looked at them and made an approximation.

    If you want to to a more direct compare look at VAX9-BFZ6-XSX5-CW2EN in the Block Explorer and compare with your results. Your rewards should be about 2 times this.

    I am on dobropool.com and have found it extremely reliable and would recommend giving it a go.
    I think there is an improvement to be had on using a Pool with less Miners. poolofd32th.club has typically 150 Miners submitting 280 nonces, whereas dobropool only has 25 Miners submitting 35 nonces.

    Rich



  • I have a single server with a 354TB plot. It scans the plots in about 28 seconds (3,300 MB/s) according to Blago's miner. I'm on burstminingclub and generally manage to maintain a 1% average on historic block shares. I don't get a deadline about 66% of the time, but when I do get them, I'd say they are around 6 hours on average. I have had many that were mere minutes, and even a 4 second one.



  • @sgabay242 said in Advice on how to improve Deadlines:

    So how big should a plot size be to generate 8 hour deadlines? 1PB? 2PB? 10PB? does the bus connectivity from SATA/USB and plot size read speed per round has anything to do with achieving better deadlines? I know it helps to rank better at your pool over slow miners, but does it help with your own overall resulting deadlines?

    The other interesting discovery is while my plot is read 140TB @ 25/s I'm looking at the pool.poolofd32th.club screen in real-time and I see people finishing submitting their deadlines for the same round in like 1 or 2 seconds, how is this possible???? I wonder if is WAN network latency involved here, and some of this miners are very close to the pool server, say ASIA, and I'm very far AMERICA?

    As an experiment, I'm looking to convert my miner to Ubuntu and use GPU CreepMiner written in C++, in theory Linux can proceses threads faster than Windows and C++ is Faster than Java (jMiner)

    Change your miner setting to report all deadlines found. You'll probably notice you have dozens and dozens of deadlines that vary between days to months. If you mean, "how big should a plot size be to generate at least 8 hour deadlines"...well, I'm not even sure how to go about trying to calculate that. I mean, deadlines found on a given plot vary by block. I'm not sure there's even a way to really guarantee such a scenario of happening, regardless of plot size (well, I guess unless someone owned 100% of the network).

    For submission, deadlines should be submitted to the pool the instance they are found (+latency), so its completely normal to see miners submitting deadlines a split second after a new block. Yours deadlines should be submitting in the same manner, even if it takes your miner 25 seconds to read your whole plot.