XPlotter for optimized plots (CPU)


  • admin

    I made a new win client release with XPlotter v1.0 included.
    By default it does not run in admin mode - but still works.

    https://github.com/dawallet/burstwindowswallet/releases/tag/0.3.8-rc5

    edit: You can run the win client in admin mode by right click on the desktop symbol. That should propagate to the XPlotter.


  • Mod

    @daWallet w/o admins rights speed the same as in v0.7



  • @Blago , how about if you specify a file size, no better than v0.7? Also, how would you do that if you were starting the program from a bat file command? Thanks,



  • @Blago This is great! I'm plotting 2TB with it now, I'll let you know how it goes in a day or two.


  • Mod

    @rds I'd tested bat file (runing as Admin) - works fine

    @setlocal
    @cd /d %~dp0 
    XPlotter_avx.exe -id 17930413153828766298 -sn 601000000 -n 1000000 -t 6 -path H:\plots -mem 6G
    XPlotter_avx.exe -id 17930413153828766298 -sn 602000000 -n 1000000 -t 6 -path H:\plots -mem 6G
    @pause
    

    time generating first plot - 3 hrs 17 min
    time generating second plot - 3 hrs 24 min
    (miner was running)


  • Mod

    @zyzzyva 2Tb = 25 hrs for me (5120 nonces/min)



  • @Blago Unfortunately I have to plot this drive on my work computer, so I'm only using 2 threads and getting about 2800 nonces/min. Hoping for < 48 hours!



  • @Blago, never sawthe @ signs in the cmd window. Is that what make it administrator? What command in the bat file tells the computer to go admin? Thanks.


  • admin

    @rds The @ signs in the bat file just prevent those commands showing on the screen. To run the bat as administrator, in Explorer, or on a shortcut, right click and select "Run as Administrator"



  • @Blago, I must be doing something wrong!! :(

    Granted I started this file with V0.7 because I just saw last night about V1.0. I started a 200GB file last night around 11:00pm it is now approaching 24 hours and it is not done yet. 765962 of 819200 nonces complete. I don't have the fanciest computer but the program reported 1024 nonces per thread. 2048MB of memory used of 4144MB free. The computer has 8GB but I'm mining with it as well. The program did the first run with 8192 nonce then started rolling after that. TaskMgr shows the xplotter is using 2053. MB of memory.

    Here was the bat file that started the program:

    pause
    c:\burst\XPlotterV0.7\XPlotter_avx.exe -id 15660867970884543098 -sn 907168001 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV0.7\XPlotter_avx.exe -id 15660867970884543098 -sn 907987201 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV0.7\XPlotter_avx.exe -id 15660867970884543098 -sn 908806401 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV0.7\XPlotter_avx.exe -id 15660867970884543098 -sn 909625601 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV0.7\XPlotter_avx.exe -id 15660867970884543098 -sn 910444801 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV0.7\XPlotter_avx.exe -id 15660867970884543098 -sn 911264001 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV0.7\XPlotter_avx.exe -id 15660867970884543098 -sn 912083201 -n 819200 -t 4 -path p:\burst
    pause
    cmd.exe

    Needless to say I'm going to stop the bat file after the first file is done.

    I will try the V1.0 tonight on a 200GB file. If I get the same result I am going back to the old plotter.


  • Mod

    @rds
    After the first file is done, close Xplotter v.0.7, update plotter, change bat file

    c:\burst\XPlotterV1.0\XPlotter_avx.exe -id 15660867970884543098 -sn 907987201 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV1.0\XPlotter_avx.exe -id 15660867970884543098 -sn 908806401 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV1.0\XPlotter_avx.exe -id 15660867970884543098 -sn 909625601 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV1.0\XPlotter_avx.exe -id 15660867970884543098 -sn 910444801 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV1.0\XPlotter_avx.exe -id 15660867970884543098 -sn 911264001 -n 819200 -t 4 -path p:\burst
    c:\burst\XPlotterV1.0\XPlotter_avx.exe -id 15660867970884543098 -sn 912083201 -n 819200 -t 4 -path p:\burst
    pause
    

    run bat as Admin.

    ***by default XPlotter uses nonces per thread = 1024 as it's the fastest size for writing at Windows (64KB chunks)



  • @Blago,

    So the v0.7 file took about 24hrs for 200GB. I ran as administrator the v1.0 and asked for 4gb memory. The file is running nicely and based on the %done, it looks like 3-3.5 hours per 200gb. About the same or maybe even a bit faster than the wplotgenerator and optimizer. Good job, thanks for all your help.



  • This post is deleted!


  • @ZapbuzZ , agreed, but I can run the two processes simultaneously at about 4 hours per 200GB. The new v6 stalled on me and the v7 took 24 hours. So I was headed back to the old system until V1.0 came out, changed for the better.



  • This post is deleted!

  • Mod

    @ZapbuzZ try set priority for XPlotter_avx = "below normal" in task manager.



  • This post is deleted!


  • For the record, my 2TB plotted with XPlotter 1.0 is mining like a charm. Thanks, Blago!



  • Happy to report I'm running Xplotter v1.0 on autopilot with average times for 200GB plots at 5.5 hours. I am running an older laptop and a new one. Both yield the same speed.

    To me, the best feature of the Xplotter over Wplotgenerator/Optimizer is when a drive disconnects or the Optimizer program hangs or stops, the partial file is lost and you have to start over. This was one of the reasons I chose to use 200GB as my base plot size. Xplotter eliminates this issue. Thanks for a great enhancement to the CPU plotting process.


  • Mod

    @rds said in XPlotter for optimized plots (CPU):

    I am running an older laptop and a new one. Both yield the same speed.

    if you see gray line (not yellow) while writing % - you need increase memory usage by -mem (better choice for nonces_per_thread = 2048. It's <threads> GB FREE RAM)


Log in to reply
 

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