XPlotter for optimized plots (CPU)
-
@rds
After the first file is done, close Xplotter v.0.7, update plotter, change bat filec:\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 pauserun bat as Admin.
***by default XPlotter uses nonces per thread = 1024 as it's the fastest size for writing at Windows (64KB chunks)
-
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!
-
@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.
-
@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)
-
The newer computer (win 10) has 8GB ram and 4 threads, I specified -mem 4GB. The cmd window says 2048 nonces/thread.
The older one (win 7) has 6GB ram and 4 threads, I specified -mem 2GB.
Can't see it in this shot but I think at the beginning it said 1024 nonces/thread.As you can see from the pics, about the same speed (3900 nonces/min) for each computer but the newer one is mining also.
The older computer sometimes shows gray, sometimes yellow.
-
@rds said in XPlotter for optimized plots (CPU):
The older one (win 7) has 6GB ram and 4 threads, I specified -mem 2GB.
Can't see it in this shot but I think at the beginning it said 1024 nonces/thread.nonces_per_thread = 2GB / 2 / 64 / 4096 / threads = 1024 nonces/thread
The older computer sometimes shows gray, sometimes yellow.
both computers have equivalent CPU.
Older will be bit slowly because calculates nonces faster than writes it.
-
@Blago can you explain the difference between the grey and yellow text? Mine changes at different percentages while plotting
-
@k.coins When ploter starts - it calculate first chunk of nonces. After calc done - it start write first chank and in parallel start calculate second chunk of nonces. Then wait until writing done...
If you see gray line - plotter calculated nonces before writing done and it wait while writing done (wasting time).
You need increase memory usage.
BUT! from my tests (HDD):
writing time of 6 * 800 nonces ~= 45 sec
writing time of 6 * 1024 nonces ~= 45 sec
writing time of 6 * 1030 nonces ~= 90 sec
writing time of 6 * 2048 nonces ~= 90 sec
-
@Blago How can I check if my Plot files are good?
Are my current methods, plotschecker and running it through your miner, still valid?
I'm asking because you'r using a new way for writing to disk.My PC crashed while plotting a 4TB disk at whole. The plot file checks out so the plotter seems to have finished.
But 4TB in about 12h, that just can't be!! ⺌∅‿∅⺌ !!I was using
@setlocal @cd /d %~dp0 XPlotter_avx.exe -id 107189002634585473 -sn 830522688 -n 15260960 -t 6 -path D:\plots -mem 20G @pause
-
@nixxda plotschecker can't help for optimized plots.
Just run again bat@setlocal @cd /d %~dp0 XPlotter_avx.exe -id 107189002634585473 -sn 830522688 -n 15260960 -t 6 -path D:\plots -mem 20G @pauseand plotter will check and continue writing. (each plot, created by XPloter 1.0 contain info - how much physically written nonces)
-
This post is deleted!
-
@ZapbuzZ when you make plot (fill drive mode) - xplotter create plot with size as possible.
If you interrupt creation - you need change bat.
for example:- XPlotter_avx.exe -id 107189002634585473 -sn 830522688 -n 0 -t 6 -path D:\plots -mem 20G
- plotter create 107189002634585473_830522688_15260960_15260960
- interrupt plotting
- change bat to XPlotter_avx.exe -id 107189002634585473 -sn 830522688 -n 15260960 -t 6 -path D:\plots -mem 20G
if you did not change bat - XPlotter will try create a new plot, but you have not free space for it
-
This post is deleted!
-
@gumbogumbo the -mem parameter is what you'll want to play with. I think it will only use half of what you have available, no matter what you put in for the value.
But just as an example, if you have 20 Gb of RAM, try using "-mem 20G" to see how much xplotter will actually utilize.



