XPlotter for optimized plots (CPU)
-
500 gb done without errors i use the burst windows client build in xplotter so you don't have to count evry thing ....
it works verry well .....
15 tb to go lets plot :)
-
just finished plotting 232GB (950272 nonces) in 10491 seconds

plotting while mining burst and nicehash

XPlotter_avx.exe -id <account> -sn 4606760 -n 950272 -t 4 -path E:\ -mem 8g
-
@zyzzyva said in XPlotter for optimized plots (CPU):
I've plotted two different 1TB drives with XPlotter so far, on two different Win7 64-bit systems, and one was good and the other gave deadline errors. One notable thing was that the bad plot was generated by the SSE4 executable (on an older system) and the good plot was generated by the AVX2 executable (on a newer system). Which versions are the rest of you using?
Yes I think their could be an issue with sse2 and sse4 code path. However in blago defense it might be the CPU. My e5800 was what I used. Later I found plots made with avx2 were error free. Would mean as an older CPU wears out unnoticed to a word file it might be seen in a plot file
-
@Burstde said in XPlotter for optimized plots (CPU):
@zyzzyva said in XPlotter for optimized plots (CPU):
I've plotted two different 1TB drives with XPlotter so far, on two different Win7 64-bit systems, and one was good and the other gave deadline errors. One notable thing was that the bad plot was generated by the SSE4 executable (on an older system) and the good plot was generated by the AVX2 executable (on a newer system). Which versions are the rest of you using?
Yes I think their could be an issue with sse2 and sse4 code path. However in blago defense it might be the CPU. My e5800 was what I used. Later I found plots made with avx2 were error free. Would mean as an older CPU wears out unnoticed to a word file it might be seen in a plot file
i dont think so, as @Blago pointed out that there's a problem in the start nonces.
I've used both AVX and SSE on three different PC/CPU but same error.
-
oh missed that. The issue is in your start nonces or plotting program?
-
For the Win Client users out there:
https://github.com/dawallet/burstwindowswallet/releases/tag/0.3.8-rc4This version includes the newest XPlotter from Blago.
-
@Burstde Yeah, @Blago found a bug with starting nonces in the code. So I think the SSE4/AVX issue I posted about was a coincidence. Although since neither plot started at 0, I wonder how the second one worked at all!
-
at this first iteration of writes plotter need much more time because OS need physically create file and fill up by zero to the end of file.
For testing - I'm creating empty file, need 5 hrs for phisically make 2Tb
-
Excited to try this. Thanks @blago
-
@Blago Looks pretty cool... I tried a small plot of 10GB or something before you announce the plotter in here and all looked ok but like i said before i have no space to try plot a larger plot but i will try your plotter as soon as i can have some to plot ;D
Thanks for this development again buddy ;P
-
Great to see you found the bug.
Just an observation, the old plotter could be shut down and when restarted would pick up with the same half made file and the final plot was viable.
The old optimizer would appear to have made a full file if the drive was disconnected during the process but the file was no good.
Anyone see the same results for the new plotter either during a controlled shutdown of the program and/or an inadvertent disconnect of the plotted drive?
-
@Blago So... this might be a little early to report, but I've been replotting all my drives with Xplotterv0.7 and I'm starting to worry about how functional these plots are.
I have over 5 Tb mining right now and I have not hit a DL in over 10 blocks. No errors found or anything, just no DLs either. It seems very unlikely that this would happen, as my mobile devices with 50 Gb have hit better (and plenty more) DLs than this 5 Tb over the past day.
Does anyone have any suggestions on how I could better check the viability of these plots? They all check ok with plotschecker.
-
@k.coins Thats the exact same problem for me. I plotted a 5TB drive with XPlotter and get no DL on my Miner.
-
@JackManMania I did create file 17930413153828766298_400000000_1618184_1618184 by XPlotter v0.7
from miner's log (testing time from 7:19 to 19:14):C:\Projects\miner\x64\Release\Logs\2016-12-28_7_19_56.log (28 hits) Line 2823: 07:34:24 found deadline=281589 nonce=400093887 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 10116: 08:14:31 found deadline=348650 nonce=401275695 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 22401: 09:36:04 found deadline=305632 nonce=401193973 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 22782: 09:37:51 found deadline=537733 nonce=400429912 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 23521: 09:42:53 found deadline=223638 nonce=400686492 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 34063: 10:51:11 found deadline=1122985 nonce=400194338 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 34321: 10:51:46 found deadline=80685 nonce=400559002 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 38029: 11:18:11 found deadline=317102 nonce=400263359 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 43243: 11:58:31 found deadline=350022 nonce=401339681 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 47887: 12:43:26 found deadline=980811 nonce=400391888 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 48377: 12:44:35 found deadline=2497999 nonce=400051445 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 50367: 13:01:24 found deadline=382649 nonce=400497431 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 63040: 14:53:37 found deadline=1317561 nonce=400743845 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 65198: 15:10:10 found deadline=1118693 nonce=401612895 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 69385: 15:41:45 found deadline=1207255 nonce=400241640 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 70614: 15:49:31 found deadline=801616 nonce=400448882 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 72696: 15:59:32 found deadline=182215 nonce=400800245 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 73709: 16:03:19 found deadline=1838315 nonce=400610152 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 77094: 16:23:45 found deadline=386656 nonce=400202428 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 78762: 16:35:32 found deadline=687911 nonce=401379258 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 81461: 16:59:35 found deadline=774723 nonce=400068198 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 85060: 17:20:01 found deadline=561413 nonce=400510233 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 88440: 17:44:02 found deadline=1647922 nonce=400159671 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 90064: 17:54:11 found deadline=533829 nonce=400031968 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 95360: 18:26:16 found deadline=2842743 nonce=400026810 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 99540: 18:59:53 found deadline=507879 nonce=400078944 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 100304: 19:05:13 found deadline=74366 nonce=401110035 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184 Line 101656: 19:12:57 found deadline=1615711 nonce=400010440 for account: 17930413153828766298 file: 17930413153828766298_400000000_1618184_1618184
-
@Blago Ok. I believe I used Version 0.6 so that might be a reason why. I might give plotting another go this weekend.
-
Last night I plotted a 200GB file with Xplotter V0.7. This morning I woke up, it was done 20029 seconds to complete.
5.5 hours to plot and optimize is slower than the old system, at least for me and the computer I'm using.
Turned on the miner with just this one file:
I still don't think all the bugs are out.
-
@rds can you send to me your log-file?
But replace your secret phrase (password) by some symbols before sending.it's my plot generated by v0.7
also I'm just finished first test v0.8, file with the same size (1.8Tb, 7630128 nonces)
v0.7 - 115671 seconds - 32 hrs 8 min (avg ~3958 nonces/min)
v0.8 - 91026 seconds - 25 hrs 17 min (avg ~5029 nonces/min) but required admin rights
-
@Blago I have some Tb replotting with v0.7 right now. I'll hook you up with the log files when finished. It'll be a while though, the plots are rather large.
Probably shouldn't have fully committed so soon lol
-
@Blago So sorry, my bad. I had downloaded v7 but did not load it into the directory my bat file was pointing to so that file shown above was made with v6.
I'm glad to see that. I'm going to plot another 200GB file right now with V7 and get back with the results.
-
I just finished plotting a 200GB file using V7. Good news and bad news.
Good news, the file is intact and produces good DLs.
The bad news, it took 6 hours and 3 minutes to finish.
To me, that is not so good. IIRC, I can plot a 200GB file in 2 hours, while, at the same time, optimizing a 200GB file at 2 hours or maybe less. So the old system is at least 3 times faster. I will do an actual test tomorrow (too late tonight) and report the times.






