XPlotter for optimized plots (CPU)
-
The other discussion was about SMR disks specifically. And as I remember my tests about cluster size were not conclusive! SMR's are using the periphery of the disk as an fast buffer (non smr) and everything inside is smr (overlapping). I read somewhere that all of this (and the controller) is very likely optimized for the default cluster size!
But we didn't have Xploter at the time! I might replot one of these disks yust to see how it "behaves"!-)
-
@Blago Wow 1.0 is way better than the GPU plotter finally I can have optimized plots good work.
Edit: Just finished plotting 6TB in one big plot file took 35 hours.
-
@blago At first, thanks for your hard work.
I have a question: Is there a way to pause the plotting and resume later. Or at least change the thread number on the fly so when I need to work I can decrease, say 2 threads, and at night I can increase to full threads.
It takes too long and I have to use my PC also for work (CPU intensive 3d modeling and rendering).
Thanks again :)
-
@umutusu In task manager you can adjust the affinity of the plotter application - take away cores from it when you need them, give them back when you don't.
-
@umutusu said in XPlotter for optimized plots (CPU):
@blago At first, thanks for your hard work.
I have a question: Is there a way to pause the plotting and resume later. Or at least change the thread number on the fly so when I need to work I can decrease, say 2 threads, and at night I can increase to full threads.
It takes too long and I have to use my PC also for work (CPU intensive 3d modeling and rendering).
Thanks again :)you can also close the window to end the plotting and just run the bat file again when your done using your PC. It will continue where it left from plotting.
-
I just wanted to thank @Blago for his work here it was so easy to setup and use.
All this work is super appreciated
@someone give this man some cookies
-
I <3 @Blago lol - as soon as I come up on some some coin, you and all the other devs will get a bonus
-
I am having problems with write speeds on my drive can anyone help? I have tried messing with the threads and mem settings but cant seem to get it right. The plotter will go through the first set of nonces fine staying completely yellow with generating and writing. But then after the first set of nonces get written my write speed drops down considerably anyone know what could be causing this?
-
@vile You run bat as Admin? NTFS?
screenshot pls
-
Yes running as admins and ntfs
-
-
wow that picture didnt work well hold on
-
-
@setlocal
@cd /d %~dp0
XPlotter_avx.exe -id 4109705781501484856 -sn 0 -n 19062264 -t 4 -path F:\plots -mem 6G
@pause
-
@vile looks fine, your drive connected to USB2 or USB3 ?
-
@vile it s your drive. The Seagate backup plus is one of those SMR drives I believe. I have a few of them and while they are having fine read speed, write is SLOooooW... it will take a while to plot it...
see more about it in this thread
-
-
I have fixed the problem by reading earlier in the thread and formatting my drive to 64kb allocation. Thanks guys everything running the way it shoudl now.
-
OK ppl I finally got the RAM usage to be where I want it to be.
Now how do you recover an incomplete plot from xplotter because it crashed on me twice while plotting a 5TB drive and this would have saved me so much time instead of starting the plotting from scratch
-
@socal when you restart the "RunThisAsAdmin.bat" with XPlotter v1.0 all you need to do is put in the number of nonces that are in your file name instead of 0 for the -n parameter. If you didn't use the -n 0 parameter to initially fill your drive and have already explicitly gave it a value for the number of nonces, you should just be able to rerun the .bat file.
the -n 0 parameter just fills the drive, so the number of nonces aren't exactly known until the plotter calculates them based on the space available and a few other things. So if you have to restart a plot that you made using -n 0, you would need to go to the plot's file name and figure out how many nonces were calculated then use that instead of 0. Hope that made sense...





