plotman VS bladebit

Yes, see https://github.com/madMAx43v3r/chia-plotter for plotting with a ramdisk and https://github.com/ericaltendorf/plotman to automate everything.

Plotman is what you want. You can plot on multiple drives (tmp), then cache the completed plots on destination drives/directories (dst). Then the archive function can rsync them to an array of archive drives. Very easy to modify the config .yaml file then run "plotman plot" and "plotman archive". https://github.com/ericaltendorf/plotman

Plotman: v0.5.1

Yeah. Plotman config guide shows you how to set it up for madmax. Its as easy as changing the "type" variable in the config file from "chia" to "madmax" and then changing your other plotting variables to what they should be be for madmax.

Madmax plotter, Swar plot manager, and Plotman plot manager all support portable plots for pools now. Others probably do, but I'm not as familiar with them. Update to the latest versions for the best results, and double-check your configuration files as some settings may have changed since your last update. And you can also use plot managers with Madmax these days, if you want to take advantage of workflow management (multiple destination drives, parallel plotting on bigger plotters, less scrolly logs, etc).

The v0.5 plotman includes support for madmax plotting as well as chia pool plotting. If you're feeling brave, update your plotman with: pip install --force-reinstall git+https://github.com/ericaltendorf/plotman@main

from the default config:

# upgrading chia to the latest version cd chia-blockchain/ . ./activate chia stop -d all deactivate git fetch git checkout latest git reset --hard FETCH_HEAD git status sh install.sh . ./activate chia init edit file: nano /home/YOURUSERNAMEHERE/chia-blockchain/setup.py change the chiapos==1.0.2 to chiapos # resolving all config problems sudo apt install aptitude sudo aptitude -f install build-essential aptitude install cmake sudo aptitude install cmake (first type n, then type y) sudo aptitude install python3-dev (first type n, then type y) cd git clone --branch combined https://github.com/pechy/chiapos.git cd chiapos mkdir -p build && cd build # configuring flags to compile CFLAGS="-mtune=native -march=native" CXXFLAGS="-mtune=native -march=native" cmake ../ 1241 cmake --build . -- -j 6 # compiling cmake --build . -- -j 6 . ~/chia-blockchain/activate cd ~/chiapos && python setup.py install # finding all old chiapos files to replace find / -name chiapos.cpython-38-x86_64-linux-gnu.so # removing old chiapos rm /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos.cpython-38-x86_64-linux-gnu.so rm /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos-0.0.0-py3.8-linux-x86_64.egg/chiapos.cpython-38-x86_64-linux-gnu.so cp /home/YOURUSERNAMEHERE/chiapos/build/chiapos.cpython-38-x86_64-linux-gnu.so /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos.cpython-38-x86_64-linux-gnu.so cp /home/YOURUSERNAMEHERE/chiapos/build/chiapos.cpython-38-x86_64-linux-gnu.so /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos-0.0.0-py3.8-linux-x86_64.egg/chiapos.cpython-38-x86_64-linux-gnu.so # reinstall plotman pip install --force-reinstall git+https://github.com/ericaltendorf/plotman@development plotman interactive in plot logs you should be able to see Using optimized chiapos - 24288eb

Nice, waiting official announce, but following are the commits looks like last 6 are commit after alpha 1: https://github.com/Chia-Network/bladebit/compare/master...cuda-compression

git checkout -b cuda-compression or git clone https://github.com/Chia-Network/bladebit.git -b cuda-compression

I don't have any epycs, but I've talked with many people who do, as well as some TR pro owners with 3000 and 5000 series, and we've tested a lot of things. https://github.com/Chia-Network/bladebit/discussions/228 describes some of the problems seen with epycs pretty well. We've also discussed using different nodes per socket settings, disabling some of the cores, manually using numactl and running bladebit with --no-numa and --no-cpu-affinity. So yes, I have some idea what I'm talking about, and your blanket statement that "bladebit doesn't use multithreading" is 100% incorrect.

If you get your CPU-not-maxed-out problem solved, you might want to try a RHEL based distro (for Bladebit). As of a year ago RHEL was noticably faster with Bladebit. This thread had positive things to say about Rocky (RHEL 8 clone). Apparently Arch is another good candidate.