GPU plotter doesnt start.



  • @PummelHummel said in GPU plotter doesnt start.:

    HGST 8TB

    I am not pro with drives but a Helium drive should not read at a speed of 6 MB/s. Maybe someone more competent will come to assist u, I have no clue what is going on with ur reading speed.

    Can u show us ur plot file? Just paste here the exact name of the file.



  • 3863229165860700817_0_29491200_8192



  • @PummelHummel This plot i not optimized and it will do no good with ur drive. Better use xplotter to plot this drive, as u have 8TB make it in small chunks like per 2 TB. The reason is because if the plots will be corrupted it will be a pain in the a$$ for u to plot an 8TB drive again so to avoid this u can easily delete the plot that is corrupted and U will need only to plot 2TB file then.

    We gonna create optimized plots for ur drive. Open xplotter folder in appData - roaming - Burst Wallet.

    U gonna see a file called RunThisAsAdmin. Edit this and u should see some command with some numbers, u gonna see something like this:

    XPlotter_avx.exe -id 3863229165860700817  -sn 0 -n 1843200 -t 8 -path D:\plots -mem 8G
    

    id = Ur burst wallet ID which is 3863229165860700817
    sn = Start Nounce (since we gonna start fresh u put 0 here)
    n = Nounces u want to plot for ur drive (We gonna create 4 plots each 2TB. 1GB = 4096 nounces. 2TB = 4096 x 200GB = 819200)
    t = Number of processor threads or core u have. If u have 8 core u put 8, if u have 4 u put 4 etc.
    path = path of the plot u want to put (in this case put ur drive path E or D or F)
    mem = Ur RAM memory available that u want it to use. If u have 16 GB RAM just use 8 its enough.

    8TB is equal to 3 276 800 nounces (that's the max ur drive can fit, so we gonna split this in 4 parts, each plot gonna have 819.200 nounces)

    First plot - Run xplotter under these settings:

    XPlotter_avx.exe -id 3863229165860700817  -sn 0 -n 819200 -t 8 -path D:\Burst\plots -mem 8G
    

    For the second plot - Run xplotter under these settings:

    XPlotter_avx.exe -id 3863229165860700817  -sn 819201 -n 1638401 -t 8 -path D:\Burst\plots -mem 8G
    

    To avoid plot overlap our start nounce for the second plot will be 819201 because we continue the plot and plots CANNOT have the same nounce ID (+1) so just add this with 819200 to get the end nounce (n) which is 1638401

    Third plot - Run xplotter under these settings:

    XPlotter_avx.exe -id 3863229165860700817  -sn 1638402 -n 2457602 -t 8 -path D:\Burst\plots -mem 8G
    

    We start with 1638402 and we end with (1638402 + 819200 = 2457602)

    Last plot - Under these setting:

    XPlotter_avx.exe -id 3863229165860700817  -sn 2457603 -n 3276800 -t 8 -path D:\Burst\plots -mem 8G
    

    We ended the nounce with 3276800 because that's the number of nounces ur drive can fit in.

    U run xplotter ONE BY ONE until plots are done. And then start mining again to see the difference of reading the plots and mining. Have fun

    PS: DONT FORGET TO RUN XPLOTTER AS ADMIN



  • Thanks for your effort. I really appreciate it!

    But Plotting 2TB with my CPU takes ~24h. Also its 4 times slower than with my GPU. This cannot be the way to go right?

    I mean if this is the only way to get working plots why is there a GPU Plotter?



  • @PummelHummel Ofc it takes time ;) Everything here takes time :)

    U can try to use gpuPlotter in Direct mode but I don't guaranty u that u gonna get an optimized plot. I don't like gpuPlotter for some reason and I like more CPU plotter even if it takes time that's the price u pay to get an ready optimized plot to be mined. Using gpuPlotter in buffer mode does not optimize ur plots hence still u have to use another application to optimize plots, for me that is a waste of time to do a job twice instead of 1 time already.

    One way or another u need to have ur plots optimized if u want to mine properly with benefits. Or u use gpu plotting and u use another program to optimize those plots (u gonna do 2 jobs so u already losing time) , Or u use Xplotter and u create optimized plot already in one time. Ur choice to make :3

    And gpuPlotter requires u to know what u are doing because u need to figure out what will be the best settings for ur GPU in the devices txt file.

    If ur GPU is connected to a screen, u can already forget about GPU plotting :), because that gpu loses his potential in plotting while he is busy powering ur screen. So in result u gonna get flashing screen to black while using gpu plotting.



  • Alright, right now I am plotting a 1 TB in direct mode with my GPU it is plotting on 20000 nonces which is 4 times faster than with my CPU.

    In a few hours we will see if the GPU miner will be working any better.



  • @PummelHummel After plotting can u paste here the name of the file generated by the gpuPlotter. I would like to see if it's optimized or not. Why didn't u plot 2TB? :) U want to split in into 8?



  • I just wantet to plot something that I can try out before going to bed. And then letting it run over night.

    Also out of 8tb there is only 7,25 TB of actual volume so I have not decided which size I will be going for. I always thought the bigger the better.



  • @PummelHummel bigger out? plot? Nope, big does not mean good xd. Like i said if ur plot will be corrupted some day u gonna have to replot again, so big takes time but small chunks quick to replace.



  • @pr0cesor thank you very much for your input. I made a lot of progress since yesterday. It seems like it is reading way faster now where it is optimized.



  • @PummelHummel Ofc it is. That's why we call it optimized plots =D



  • Its just weird that the CPU Miner was able to mine on the unoptimized plots and the GPU miner wasnt.


Log in to reply
 

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