Plot file scanning speed



  • Hi, I'm newbie here, first time posting :)
    I guess I'm having problems with scanning plot files, have tried 3 different miners, thanks to their creators they all are easy to use

    1. creepMiner (https://github.com/Creepsky/creepMiner) ~ 20 mb/s
    2. jminer (https://github.com/de-luxe/burstcoin-jminer) ~ 50 mb/s
    3. Blago's miner (https://github.com/Blagodarenko/miner-burst/releases) ~ 30 mb/s

    I've seen many posts of others that report 120-250 mb/s and I cannot figure out what I'm doing wrong

    I have 2 plot files for now, 1.9tb and 5.3tb

    and here are my hardware specs

    Asus h270f motherboard
    Intell 7700k
    32GB RAM(ddr4)
    MSI GTX 770 2gb Graphic card
    8TB WD external HDD

    HDD is connected to USB3 port, actually tried with all existing USB3 ports on my machine, even tried with USB 3.1 port

    what i'm doing wrong? :-/

    Thanks everyone in advance.



  • Are the plot files optimized? I saw a speed difference of 20 to 95MBps with creep on optimized vs unoptimized.



  • Hi, thank you for answer

    no, they are not yet optimized, new HDDs are yet to come, I'll try to optimize as soon as they arrive
    but I saw people reporting 100+ speed without optimized plots :-/ Aren't they telling the truth? :-)



  • I'm using gpuplotgenerator (direct mode) and I'm stuck at 0.04% plotting for 5-6 hours now :/. Some say that its normal for plotting to hang on direct mode but no one said for how long.
    My disk showed as (almost) 100% full immediately after I started plotting and I see in task manager that the disk is 100% active. What should i do?



  • @x40st said in Plot file scanning speed:

    Hi, I'm newbie here, first time posting :)
    I guess I'm having problems with scanning plot files, have tried 3 different miners, thanks to their creators they all are easy to use

    1. creepMiner (https://github.com/Creepsky/creepMiner) ~ 20 mb/s
    2. jminer (https://github.com/de-luxe/burstcoin-jminer) ~ 50 mb/s
    3. Blago's miner (https://github.com/Blagodarenko/miner-burst/releases) ~ 30 mb/s

    I've seen many posts of others that report 120-250 mb/s and I cannot figure out what I'm doing wrong

    I have 2 plot files for now, 1.9tb and 5.3tb

    and here are my hardware specs

    Asus h270f motherboard
    Intell 7700k
    32GB RAM(ddr4)
    MSI GTX 770 2gb Graphic card
    8TB WD external HDD

    HDD is connected to USB3 port, actually tried with all existing USB3 ports on my machine, even tried with USB 3.1 port

    what i'm doing wrong? :-/

    Thanks everyone in advance.

    (someone already mentioned optimizing as a first step, thats likely it, but just in case, lets explore some other reasons why you may be getting varied results or see others perform better than you, but PLEASE start with optimizing, always try to create plots in direct mode or optimized by default, its just so much better)

    some miners are using multiple hard drives, so the read times they are posting are depending on the software combined into a single stream, some people get 650MB/s because they have 16 hard drives daisy chained on USB when each individual drive is only reading at lets say 80MB/s in this scenario...

    also it could be the software you're using only allows your system to read so much data at a time, for example, when I use the one CPU miner with AVX I am only able to get 80MB/s reads while someone using the same miner with AVX2 is able to get 120MB/s reads because the software is able to use the CPU in different ways, which will lead the the same HDD performing at different rates...

    the next could just be your hard drive isn't capable of doing anymore, it could be a windows setting is set to conserve and restrict what your drive is doing because you want power savings over performance, there are a couple often mentioned things related to this such as changing the write-cache to be enable, or selection high performance in your power settings, etc etc etc...

    ultimately I don't know why your drives are performing different than their drives, but there are numerous reasons, having the i7-7700k processor means you should be able to use AVX2 instructions, so when you use a miner that has a different file for that, I suggest using it, if you're using the GPU miner then you could just be hitting a sheer wall of performance for your particular drive, or maybe you can tinker with the windows settings to ensure none of them are restricting your performance to conserve power, etc etc etc...

    what you could do, is also down crystaldiskmark and test your drives speed, so you get a baseline of what its capable of, not what you should expect from mining, but at least you know its capable of "x" even if mining will only get you "y"... I say this because my drives can get 240MB/s reads sequentially, however I will get roughly 160MB/s on average while reading using the particular GPU miner, but if I were to use the CPU miner, I would be limited to 80MB/s because I am only able to use AVX instructions and thus my performance bottleneck is the processors ability to use modern day tools... anyhow hope this helps you track down things and find a solution for yourself...

    P.S. optimizing may be your solution because your hard drive is playing wack-a-mole jumping around trying to grab bits and pieces of data to string together the information it needs, which may be slowing your whole process down as each device is waiting for your drive to provide it what it wants... but I added in all the other information above since someone else already mentioned that... (just in case)



  • @burstbubble said in Plot file scanning speed:

    I'm using gpuplotgenerator (direct mode) and I'm stuck at 0.04% plotting for 5-6 hours now :/. Some say that its normal for plotting to hang on direct mode but no one said for how long.
    My disk showed as (almost) 100% full immediately after I started plotting and I see in task manager that the disk is 100% active. What should i do?

    what version are you using, prior to v4.1.1 there was an issue in direct mode that sounds like you're hitting, where it stalls and people talk of a long pause and wait and nothing happening... make sure to use v4.1.1 or newer for direct mode, it creates a blank plot file first and then fills it in which apparently solves the hang some folks were having... in the image below you can see where the version number is when it starts up, right at the top there...

    https://github.com/bhamon/gpuPlotGenerator/releases

    the above link is all the releases he has for the software, make sure you're up to date...

    0_1498859389005_1000GB at 28019 nonces.png



  • @x40st Did you format the disk before creating your plots?



  • Hi all, I am using a 4.1.1 version and yes, I formated the disk before plotting..
    The thing is that I don't see the "progress" that others are saying. When I started plotting, disk showed as full immediately. I set up only one plot. Should I try the newer version of gpuplotter? :/



  • @burstbubble Version 4.1.1 needs to be run as administrator.


  • admin

    @burstbubble Are you sure it's 4.1.1? The behaviour you're describing is typical of prior versions.

    Can you post a screen shot including the command line, and everything up to where it's currently reporting progress.



  • 0_1498890481927_Clipboard01.jpg Here is the screenshot...any ideas?



  • @burstbubble Your stagger size is incorrect, try 8448 instead of 8192.

    Your stagger must divide the number of nonces by a multiple of 8.

    1858560 / 8 = 232320

    The factors of 232320 are (http://www.numberempire.com/1858560)
    1, 2, 3, 4, 5, 6, 8, 10, 11, 12, 15, 16, 20, 22, 24, 30, 32, 33, 40, 44, 48, 55, 60, 64, 66, 80, 88, 96, 110, 120, 121, 128, 132, 160, 165, 176, 192, 220, 240, 242, 256, 264, 320, 330, 352, 363, 384, 440, 480, 484, 512, 528, 605, 640, 660, 704, 726, 768, 880, 960, 968, 1024, 1056, 1210, 1280, 1320, 1408, 1452, 1536, 1760, 1815, 1920, 1936, 2112, 2420, 2560, 2640, 2816, 2904, 3072, 3520, 3630, 3840, 3872, 4224, 4840, 5120, 5280, 5632, 5808, 7040, 7260, 7680, 7744, 8448, 9680, 10560, 11264, 11616, 14080, 14520, 15360, 15488, 16896, 19360, 21120, 23232, 28160, 29040, 30976, 33792, 38720, 42240, 46464, 56320, 58080, 61952, 77440, 84480, 92928, 116160, 123904, 154880, 168960, 185856, 232320, 309760, 371712, 464640, 619520, 929280, 1858560

    8448 is in this list 8192 is not.

    Cancel your plot, then try it again with stagger size of 8448
    (Be sure to permanently delete the old plot first)

    Let us know if you have an issue.



  • @iKnow0 Now it hangs at 0.06% :D...



  • @Darkbane said in Plot file scanning speed:

    @x40st said in Plot file scanning speed:

    Hi, I'm newbie here, first time posting :)
    I guess I'm having problems with scanning plot files, have tried 3 different miners, thanks to their creators they all are easy to use

    1. creepMiner (https://github.com/Creepsky/creepMiner) ~ 20 mb/s
    2. jminer (https://github.com/de-luxe/burstcoin-jminer) ~ 50 mb/s
    3. Blago's miner (https://github.com/Blagodarenko/miner-burst/releases) ~ 30 mb/s

    I've seen many posts of others that report 120-250 mb/s and I cannot figure out what I'm doing wrong

    I have 2 plot files for now, 1.9tb and 5.3tb

    and here are my hardware specs

    Asus h270f motherboard
    Intell 7700k
    32GB RAM(ddr4)
    MSI GTX 770 2gb Graphic card
    8TB WD external HDD

    HDD is connected to USB3 port, actually tried with all existing USB3 ports on my machine, even tried with USB 3.1 port

    what i'm doing wrong? :-/

    Thanks everyone in advance.

    (someone already mentioned optimizing as a first step, thats likely it, but just in case, lets explore some other reasons why you may be getting varied results or see others perform better than you, but PLEASE start with optimizing, always try to create plots in direct mode or optimized by default, its just so much better)

    some miners are using multiple hard drives, so the read times they are posting are depending on the software combined into a single stream, some people get 650MB/s because they have 16 hard drives daisy chained on USB when each individual drive is only reading at lets say 80MB/s in this scenario...

    also it could be the software you're using only allows your system to read so much data at a time, for example, when I use the one CPU miner with AVX I am only able to get 80MB/s reads while someone using the same miner with AVX2 is able to get 120MB/s reads because the software is able to use the CPU in different ways, which will lead the the same HDD performing at different rates...

    the next could just be your hard drive isn't capable of doing anymore, it could be a windows setting is set to conserve and restrict what your drive is doing because you want power savings over performance, there are a couple often mentioned things related to this such as changing the write-cache to be enable, or selection high performance in your power settings, etc etc etc...

    ultimately I don't know why your drives are performing different than their drives, but there are numerous reasons, having the i7-7700k processor means you should be able to use AVX2 instructions, so when you use a miner that has a different file for that, I suggest using it, if you're using the GPU miner then you could just be hitting a sheer wall of performance for your particular drive, or maybe you can tinker with the windows settings to ensure none of them are restricting your performance to conserve power, etc etc etc...

    what you could do, is also down crystaldiskmark and test your drives speed, so you get a baseline of what its capable of, not what you should expect from mining, but at least you know its capable of "x" even if mining will only get you "y"... I say this because my drives can get 240MB/s reads sequentially, however I will get roughly 160MB/s on average while reading using the particular GPU miner, but if I were to use the CPU miner, I would be limited to 80MB/s because I am only able to use AVX instructions and thus my performance bottleneck is the processors ability to use modern day tools... anyhow hope this helps you track down things and find a solution for yourself...

    P.S. optimizing may be your solution because your hard drive is playing wack-a-mole jumping around trying to grab bits and pieces of data to string together the information it needs, which may be slowing your whole process down as each device is waiting for your drive to provide it what it wants... but I added in all the other information above since someone else already mentioned that... (just in case)

    Thank you very much for the detailed answer!
    I will report back with results!


Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.