XPlotter for optimized plots (CPU)
-
This post is deleted!
-
@Rendavu said in XPlotter for optimized plots (CPU):
how do i calculate to plot only 250gb and then the next plot 250gb can you give me a example?
XPlotter_avx.exe -id 1507623489964157959 -sn 600000000 -n 0????? -t 7 -path f:\
does it really need to start at 600000000 when plotting?
-
@Yey_09 said in XPlotter for optimized plots (CPU):
@Rendavu said in XPlotter for optimized plots (CPU):
how do i calculate to plot only 250gb and then the next plot 250gb can you give me a example?
XPlotter_avx.exe -id 1507623489964157959 -sn 600000000 -n 0????? -t 7 -path f:\
does it really need to start at 600000000 when plotting?
No, you can choose whichever starting nonce you would like. Make sure that you choose a starting nonce that does not overlap with your other plots. If it is your first plot, you can start from 0 for instance.
-
Are there any advantages or disadvantages to having Xplotter in the same drive that is being plotted? Could it be faster if the plotter was on a different drive?
0Create a unique Burst account ID with Luxe's vanity generator: https://github.com/de-luxe/burstcoin-address-generator/releases
BURST-E2NW-8UXH-92YR-BALLS
one_reply_to_this_post
-
@Propagandalf
Xplotter location does not matter for performance.p.s. next version must be faster :)
-
@Blago said in XPlotter for optimized plots (CPU):
@Propagandalf
Xplotter location does not matter for performance.p.s. next version must be faster :)
does the size of ram to be used can be adjusted? cant wait to try it.
-
Last night I set up a bat file to plot 3, 200gb files, when I went to bed 134,224 nonces were displayed of 819200 total for the first file. Those took 2 hrs, 12 minutes. This morning the xplotter was "stalled" at 144155 nonces. When I started the xplotter, the memory used was ~2550 MB of 8GB ram as the optimizer program was running using 3072 mb and I was mining, as well. Also a bitcoin node was running which really doesn't use any appreciable amount of system recourses.
Here is the bat file:
pause
c:\burst\XPlotter.v0.6\XPlotter_avx.exe -id 15760867970884553098 -sn 900000001 -n 819200 -t 4 -path m:\plots
c:\burst\XPlotter.v0.6\XPlotter_avx.exe -id 15760867970884553098 -sn 900819201 -n 819200 -t 4 -path m:\plots
c:\burst\XPlotter.v0.6\XPlotter_avx.exe -id 15760867970884553098 -sn 901638401 -n 819200 -t 4 -path m:\plots
pauseAny thoughts?
-
@rds said in XPlotter for optimized plots (CPU):
Last night I set up a bat file to plot 3, 200gb files, when I went to bed 134,224 nonces were displayed of 819200 total for the first file. Those took 2 hrs, 12 minutes. This morning the xplotter was "stalled" at 144155 nonces. When I started the xplotter, the memory used was ~2550 MB of 8GB ram as the optimizer program was running using 3072 mb and I was mining, as well. Also a bitcoin node was running which really doesn't use any appreciable amount of system recourses.
Here is the bat file:
pause
c:\burst\XPlotter.v0.6\XPlotter_avx.exe -id 15760867970884553098 -sn 900000001 -n 819200 -t 4 -path m:\plots
c:\burst\XPlotter.v0.6\XPlotter_avx.exe -id 15760867970884553098 -sn 900819201 -n 819200 -t 4 -path m:\plots
c:\burst\XPlotter.v0.6\XPlotter_avx.exe -id 15760867970884553098 -sn 901638401 -n 819200 -t 4 -path m:\plots
pauseAny thoughts?
you tried to do 3 plots, all at the same time?
-
No, one after the other, the last two commands never executed because the first never finished.
-
@rds yesterday i'm delete all plots at my 2 Tb HDD and run xplotter
XPlotter_avx.exe -id 17930413153828766298 -sn 100000000 -n 0 -t 6 -path L:\plots\17930413153828766298_100000000_7630160_7630160
25 hrs, still works...
seems sometimes xplotter is stuck (but not in my case), now i'm making new version (change the algorithm, fixing issues)
edit:
32 hrs 8 min (avg ~3958 nonces/min)
-
6tb is still plotting and more days to come :) next time smaller plots ;)
-
@Rendavu Yes I'm at 6TB as well been going for three days.
-
To add to my previous post about the stalled xplotter. Today I found the first file of my 3 in the bat file in the plot directory intact and checked ok by the plotchecker program. So the xplotter plotted a 200GB optimized file in some time between 4 and 8 hours (from the time I went to bed to the time I closed out the xplotter when it appeared to be stalled).
I still am using the old plotter and optimizer. I plot a 200gb file in about 2-3 hours while concurrently optimizing 2-200gb files. FYI
-
6tb is complete no i'am getting this error 1007 what can i do just wait??
0My address BURST-LD29-LG97-Z2JT-393VB
Get more burst coins http://burstcoin.biz/surfbar?ref=3463
2 Replies
-
After two days of replotting and having the same error I go back plotting using wplotgenerator.
Error on file is intermittent.
PC #1
HDD#1 3.5 - 1 plot 265GB - OK
HDD#2 2.5 - 1 plot 111GB - OKPC#2
HDD#1 3.5/2 partition - 1 plot 200GB - "Fast file or Corrupted Error" replot 2 times same error, currently replotting using wplotgeneratorPC#3
HDD#1 3.5 - 2 plots 232GB/233GB - OK
HDD#2 External 2.5/1TB/USB 3.0 - 4 plots 230GB each - "Fast file or Corrupted Error" replot 2 times same error, currently replotting using wplotgenerator
-
PC#3
1st plot done, no error currently miningHDD#2 External 2.5/1TB/USB 3.0 - 4 plots 230GB each - "Fast file or Corrupted Error" replot 2 times same error, currently replotting using wplotgenerator
-
@Rendavu By any chance do you have a mesage saying that your nonces are not a multiple of 8?
Or that or your plot is corrupted in some way... Either way you will have to replot!
-
i will check that again when im back home !
-
So I just finished plotting 750 Gb with the XPlotter and I'm getting some strange NOT confirmed DL messages that I've never seen before:
Everything checks out ok with the PlotsChecker:
Anyone have any ideas about what's goin on here?
-
@k.coins It's nothing to due with your plots. That message comes when the pool doesn't acknowledge the DL that you submitted. This can happen in many ways such as the pool is to busy when all of a sudden the sever gets flood with deadlines and doesn't respond to some, or there may have been a intermediate connection problem ether in sending or receiving the response. Anyway the pool most likely got and processed your deadline which means all is good, but you just didn't get a response (Which isn't the worst thing).
If this really bothers you then open a second mining window and you'll see that the second time your drives are scanned and submitted you'll get a response.
Although I've never seen the Really Bad deadline error lol.
