XPlotter for optimized plots (CPU)
-
I'm just starting out with Burstcoin and my plan is to mine using 10TB. Right now, I'm plotting simultaneously on two vastly different machines. Both are writing to identical 1TB drives. One is a home-built PC with a 3-core AMD A6-3500 and 8GB of ram:

The other is an HP workstation with dual E5-2670s and 64GB of ram:

Quite a difference. :-D
As others have experienced, the bottleneck on the HP is write speed, and watching that has me wondering about how RAM and threads affect performance.
I get that the amount of RAM allocated to plotting determines the stagger size. So then is the stagger the number of nonces generated per pass ("Generating nonces from xxxxxxx to yyyyyyy")? So the more RAM allocated, the more nonces created per pass? And then the number of threads and processor speed determines how fast nonces are generated?
Thank you blago for your work on this. And thank you to everyone else contributing. I've been digging through the forums for the past few days trying to wrap my head around all this and have found a ton of great info here. I hope to be up and mining by the weekend.
-
@RatPatrol better when nonces_per_thread = multiple by 1024.
In your case try -t 30 -mem 30G (will 2048)
or -t 30 -mem 45G (will 3096)
-
@Blago said in XPlotter for optimized plots (CPU):
@RatPatrol better when nonces_per_thread = multiple by 1024.
In your case try -t 30 -mem 30G (will 2048)
or -t 30 -mem 45G (will 3096)Thanks for the tip. I'll give it a try this weekend.
-
@Blago said in XPlotter for optimized plots (CPU):
@RatPatrol better when nonces_per_thread = multiple by 1024.
In your case try -t 30 -mem 30G (will 2048)
or -t 30 -mem 45G (will 3096)@Blago didn't quite understand your tip. What do you exactly call nonces_per_thread?
-
@vExact You want the memory allocated to be a 256MB multiple of the number of CPU threads you're allowing.
Basically, you want (allocated memory) / ( allocated threads) to be a number that ends in 0, 0.25, 0.5 or 0.75 for best performance.
-
XPlotter_sse.exe -id 737562325338747394 -sn 1007628177 -n 3648000 -t 10 -path F:\plots -mem 20G
pauseWhy is it only using 4080 mb ram?
-
Update to newest xplotter corrected it lol
-
I just finished plotting a 2tb hdd with xplotter. The total time needed for plotting and optimizing is actually faster on my machine then old method. Pc didnt get as warm and seemed to run smoother. I polotted on hp z600 2x x5550 24gb ram.
Now have a couple questions and suggestions. I noticed if I plot 200gb and stop the plotter half way the file will show 200gb but doesnt say you only filled half full with nounces. Will plot checker see that? A new person might not realize what happened. Could a check be put in place to summarize what is still empty on that file or a warning?
Can you add a pause? Make program stop at certain point and restart at your command. Sometimes I run into heat issues and just letting cool down i could avoid aborting. Of course keeping computer dust free helps out too lol
-
@tross said in XPlotter for optimized plots (CPU):
I just finished plotting a 2tb hdd with xplotter. The total time needed for plotting and optimizing is actually faster on my machine then old method. Pc didnt get as warm and seemed to run smoother. I polotted on hp z600 2x x5550 24gb ram.
Now have a couple questions and suggestions. I noticed if I plot 200gb and stop the plotter half way the file will show 200gb but doesnt say you only filled half full with nounces. Will plot checker see that? A new person might not realize what happened. Could a check be put in place to summarize what is still empty on that file or a warning?
Can you add a pause? Make program stop at certain point and restart at your command. Sometimes I run into heat issues and just letting cool down i could avoid aborting. Of course keeping computer dust free helps out too lol
Plotchecker won't id that half filled condition. And the file will mine with no errors. You have to run the xplotter with the parameters (starting nonce, # of nonces) of the file and watch it say that the file is done to insure the file is complete.
-
@rds I know that and you know that but what new guy? There was a post how a new miner couldnt get a dl and now I think I know why. He used xplotter it may of crashed he looked at file and looks complete. checks with plot checker all is ok then he mines with no nonces and getting no errors . So there you have it we also have Ghost Nonces!
-
@tross That's interesting! It could definitely make people mine ghost nonces and get no DLs if what you are saying is true.
-
@Propagandalf I was plotting my 2tb and had to cut it off cause 1 cpu got hot. well after looking at file it showed that 2tb was full. I knew it wasnt so i tried to mine with it. The miner say you have 2tb plot and mines like normal. But in reality the plot isnt all the way done only the structure is finished. Ghost nonces lol
-
-
I have also encountered this problem, plotting a drive with bad sectors, after 20 minutes said the drive was full and plots checker said everything was a ok 👌 when in fact I know it's impossible to plot 1.3tb in a half hour or so, at least not on my machine
-
Plots checker doesn't work for optimized plots, i.e. the plots xplotter creates
-
Hello everybody
I would like to know if is neccessary to optimise my disk if i plot my disk with the new nrs version 1.2.8?
Bests regards
-
I have a quick Question, why are u using FILE_FLAG_NO_BUFFERING ?
I made some tests and i'm a lot faster, when i write to ssd 100gb files which i move after creation to my external Drive and then create another 100gb file and so on.
What in your algorithm is the "optimized" part? which makes a plot ideal ?
-
@Zaziki plotting in " direct mode " or not buffering mode is what made the GPU plotter plot optimised not sure about Xplotter but i would assume its a simmiler coding
-
ah thanks, that means that a plot with multiple files is not ideal, since they are never straight written like a rail
-
@Zaziki What do u mean? If u have 8TB of drive believe me u don't want to plot a single file big as 8TB in it because if that plot will be corrupted u will end up re-plotting that big drive again, gl with that.
What u want to do in this case is to split plots into 4 or 8. If u split the plots into 4 u plot the drive for 2TB each of the plots, 1TB each if u want to split it in 8 chunks. And then if one of ur plots will be corrupted u will end up only re-plotting what is corrupted and not the whole drive as before.
Having multiple plots in a single hard drive is better than 1 packed plot, the drive also make it easy to read small chunks of plots instead of a big one.







