chia-gigahorse VS bladebit

At least with Gigahorse (by madmax) which you also need to use his farming software, not compatible with official client from Chia. https://github.com/madMAx43v3r/chia-gigahorse/tree/master/cpu-plotter

2080 super is pretty close in performance to a 3060 ti, so you can just go by this chart minus 10% or so: https://github.com/madMAx43v3r/chia-gigahorse

This is not official CNI software so proceed with caution: https://github.com/madMAx43v3r/chia-gigahorse

I don't know too much about farming with harvesters (I don't have any). What I do know is that the most recent Gigahorse release now allows for "remote GPU farming" (or whatever he is calling it) which means you will only need one GPU (in the farmer) to handle all harvester's compressed plots. As far as CPU compressed plot farming with harvesters...I couldn't tell you. Have you checked out Max's GitHub, it might answer a lot of your questions.

Gigahorse 1.7.0 upwards to 1.8.0 giga 10 https://github.com/madMAx43v3r/chia-gigahorse/releases/tag/v1.8.0.giga10

Sorry, I don't have the chia client on this machine. I only have the MadMax Windows release from this page: https://github.com/madMAx43v3r/chia-gigahorse/releases

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.