chia-plotter VS bladebit

The original Madmax plotter supports both K33 and K34, https://github.com/madMAx43v3r/chia-plotter

I didn’t use madmax for like 8 months so I don’t remember, but checkout the default number here https://github.com/madMAx43v3r/chia-plotter The thread number is depending on how many thread your cpu got. I think the more thread is better. Try to put thread = 36 and buckets = 256

I would suggest canceling and plotting with the Chia POS plotter. For testing, the Chia POS plotter should be fast enough. The madMAx plotter is generally faster but it has had issues plotting from the Chia Network client in the past. If you want to use the madMAx plotter, I would suggest using the standalone version directly from madMAx's github (which has a link to the github that does windows compiles in the install directions).

git clone https://github.com/madMAx43v3r/chia-plotter.git

No need to reverse engineer anything. It's explained in all the detail you need in the Chia Proof of Space Construction document. It's implemented in chiapos though I find madmax's implementation of the plotter to be easier to read: https://github.com/madMAx43v3r/chia-plotter/tree/master/include/chia

The article you mentioned said that all the questions about the madmax plotter has to updated on its official GitHub repo, https://github.com/madMAx43v3r/chia-plotter, so I made a copy of the same complained and updated it onto the official madmax plotter repo (and the link was given by the official chia repo).

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

The OP can try using the non-packaged version https://github.com/madMAx43v3r/chia-plotter

You can get around this by using the standalone version of madmax or setting your temp directory as your final directory and using a script to monitor and move .plot files to your final directory.

You can install madmax directly (or use the compiled windows binary). Disclaimer: neither are officially endorsed but I've used them with no issues.

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.