BzMiner Release v23.0.2

BzMiner v23.0.2


x Nvidia Blackwell (50 series support for all algos)
x Warthog updates - fixed dual CPU rigs
x Warthog optimizations/stability (too many to list, mostly backend efficiency stuff)
x Note: Warthog can take quite a lot longer to ultimately settle on what it thinks is the best hashrate, 30+ minutes sometimes

x New options:

- warthog_shaquality_mod        Percentage to adjust the warthog balancer. positive values can increase sha quality (at the potential expense of verus hr),
                                negative values will produce lower quality sha hashes from the gpu, but can keep the cpu more busy, potentially increasing
                                hashrate at the potential expense of pool hr (lower quality hashes means more hashes, but because they are lower quality
                                the chance of them being a valid share is less). default is 0.0

- cpu_threads_priority          cpu worker thread priority. 0 = low, 1 = below normal, 2 = normal, 3 (default) = above normal, 4 = high
                                (careful with 4 and 5, can halt system if using all threads), 5 = time critical

- cpu_threads_cache_group       Changes the way bz groups threads in order to maximize cache hits. Default 0 (try grouping by l3 cache).
                                1 = all threads in one group (per cpu). 2 is highest cache/grouping level in cpu topology. higher means more groups,
                                10 might mean each thread is grouped by itself if there were less than 10 groups in the cpu topology. This is a multi-dimensional array,
                                one value for each algo, same as --cpu_threads.

- cpu_affinity                  Hex string representing which cpu logical processors a mining algorithm should pin its threads to, and how many threads to launch.
                                default is 0 and will let the miner decide. every bit in the hex string represents whether a logical processor is going to mine or not.
                                Multiple hex strings can be provided in the case of more than one algorithm is being mined. An example for a 32 core cpu,
                                having every other core mined is '55555555', or to have the first half of the cores mine 'FFFF0000'. Look into thread affinity
                                (windows vs linux) and logical/physical cores (a physical core may have 2 logical cores, but they may not be next to each other
                                in the affinity, which is why you may want to either use 55555555 for even core or FFFF0000 for the first half of logical cores)
								For dual or more CPUs, can provide number of threads for each cpu, such as "15,16" if you want 15 threads on the first cpu,
                                and 16 threads on the second cpu

- mgmt_thread_affinity_mask     Hex string representing which cpu logical processors bzminer's management threads should NOT be allowed to run on. This is a mask
                                so by default it matches cpu_affinity, meaning management threads will run on logical processors that worker threads will not utilize.

- split_cpu_by_level            By splitting the CPU at level (for example, numa node, level, l3 cache, etc), bz will create multiple cpu devices,
                                one for each of the level groups.

- gpu_numa_node                 This allows you to dedicate a gpu to one or more numa nodes. Right now only used on warthog. The format is {gpu}|{node index},
                                and space separated options. For example, to dedicate gpu 0 to node 1, 2, and 3, and gpu 1 to node 0, you would do `0|1 0|2 0|3 1|0',
                                you may also use gpu pci ids like this `33:0|0 8:0|1` which would bind gpu 33:0 to node 0 and gpu 8:0 to node 1

- disable_avx512                Disable avx512 support/optimizations.

- disable_avx                   Disable avx support/optimizations.

- disable_sse                   Disable sse support/optimizations.

- disable_huge_pages            Disable Huge pages support.

- watchdog_no_new_work_seconds  If no new work is received (after pool connects and received initial work) for this many seconds, reconnect.

- debug                         Enable debug settings, equivalent to -v4 --clear_log_file 1 --log_file_verbosity 4 --show_pending --log_solutions 1 --immediate_log --log_date 1

Downloads links

Checksums

bzminer_v23.0.2_windows.zip:
MD5: a358cec5e5d70beb435e2288f9b5ec18
SHA256: aac6880f95eca4278e51dead91e15c27742fd63cd1686f5e131bc0b057ac2e02

bzminer_v23.0.2_linux.tar.gz:
MD5: 493554e9898febdb38894fc9ac766222
SHA256: 442aacceb30e3ea33fa12a8a3511380936a9a29fdbce47d49674d5f307438d99

Install scripts

MMPOS: (Note: put in Initiate command prior to miner launch field in miner profile ->advanced) 

export version="23.0.2" # Example version
if [ -f "/tmp/bzminer_v${version}_linux.tar.gz" ]; then
exit 0
else
cd /tmp; wget https://bzminer.com/downloads/bzminer_v${version}_linux.tar.gz; tar -xvf bzminer_v${version}_linux.tar.gz; sudo cp -adpR bzminer_v${version}_linux/bzminer /opt/mmp/miners/bzminer/
fi

Minerstat: 

export version="23.0.2"; mstop; cd /tmp; wget https://bzminer.com/downloads/bzminer_v${version}_linux.tar.gz; tar -xvf bzminer_v${version}_linux.tar.gz; sudo cp bzminer_v${version}_linux/bzminer /home/minerstat/minerstat-os/clients/bzminer; mstart

Hive OS: 

wget https://bzminer.com/downloads/bzminer_v23.0.2_linux.tar.gz; tar -xvf bzminer_v23.0.2_linux.tar.gz; miner stop; cp bzminer_v23.0.2_linux/bzminer /hive/miners/bzminer/22.0.0/; miner start

Rave OS: 

stop && wget https://bzminer.com/downloads/bzminer_v23.0.2_linux.tar.gz && tar -xvf bzminer_v23.0.2_linux.tar.gz && cp -adpR bzminer_v23.0.2_linux/bzminer /app-data/miners/bzminer-22.0.0 && start