-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Linux CLI plotting is way slower then GUI plotting #18582
Comments
Hey @oe3gwu , can you provide the parameters being used for both the CLI and GUI plotting? GUI
For the cli also please provide the command being used but be sure to redact your farmer public key and the contract address or pool public key |
Hello @BrandtH22 ! Sorry for the delay. I today came home from hospital and I am sick. I update this call in 1 or 2 days. Sorry again! |
This was my script. I know I technically dont need so many threads, still I wanted to be as similar as the GUI defaults are.
I tried also with bigger cache. It usually takes me approx 80min for a GUI Plot. Using this script it takes 6 - 8 hours. /mnt/void is a tmpfs ramdisk that is 2tb in size. /mnt/farm01 is a sata hdd with 18tb. Regarding parallel plotting, this is something I wanna do when this script works fine. But I want to have the same performance as in the GUi. For the GUI plot, I dont have any special options I set. Just the 2 directories, and I makr /mnt/void as RAMDisk. Nothing else. Thank you! |
chia plots create will use the chiapos original plotter chia plotters uses the newer high speed plotter both mad max and bladebit. I think the issue is the GUI is using a high speed plotter but on the command line you are using chiapos. That would make perfect sense given the speed differences. Let us know! Sorry you have been sick btw! |
I will try tomorrow. Thanks! I honestly I thought that the default CLI plotter is the default GUI plotter too. I didnt know that it falls back to |
It works better now. Still not as fast, but I guess it is a config thing. Thank you! |
What happened?
I wrote a bash script where I start a plot of 24 or 48 threads. Using the GUI it usually completes in 80 minutes. Using the CLI the plot takes 4-6 hours (I can make tests if needed). As far as I know as stupid user, all the parameters are the same on CLI as are in the GUI. On the CLI I can saturate 2 threads, not more in Phase 1.
If needed I can provide my scripts.
Version
2.4.3
What platform are you using?
Linux
What ui mode are you using?
GUI
Relevant log output
The text was updated successfully, but these errors were encountered: