ccminer-x16r VS T-Rex

https://github.com/todd1251/ccminer-x16r/releases/tag/2.2.5 - ccminer-x16r

https://github.com/trexminer/T-Rex/wiki/WebUI Also their discord has a lot of good info about setting it up

Just all your other rigs you can add as nodes, so you can see them all at once. https://github.com/trexminer/T-Rex/blob/master/README.md

MoneroOcean. Two copies of MO-xmrig fork in separate folders. Set one for CPU only. Set other for CUDA which also needs (MO-xmrig-cuda plugin fork)[https://github.com/MoneroOcean/xmrig-cuda/]) added to that folder. Then once all that works add (meta-miner)[https://github.com/MoneroOcean/meta-miner/] to the GPU folder and configure T-Rex for the algos xmrig doesn't do (autolykos2, kawpow, ethash).

T-Rex miner https://github.com/trexminer/T-Rex/releases

Download W10/11: https://github.com/trexminer/T-Rex/releases/download/0.25.12/t-rex-0.25.12-win.zip

miner stop && cd /tmp && wget https://github.com/trexminer/T-Rex/releases/download/0.25.12/t-rex-0.25.12-linux.tar.gz && tar -xvf t-rex-0.25.12-linux.tar.gz && cp /tmp/t-rex /hive/miners/t-rex/0.25.9/ && miner start

... there's that ticky word again: 'never'. https://github.com/trexminer/T-Rex/issues/508 "Trex miner memory usage keep increasing till the ram is completely full causing a system crash." This is not the only thread out there like this. Again.. last year NHQM's footprint, with some drivers, would grow to gigabytes over the course of a week. With OCtune closed. In this case, as in T-Rex complaints, the orphaned ram owner is the application, not the driver. You could see it in task manager. You could dispute this with me, but you will have to tell me I'm blind and call me a liar first.

PS. If you know what you are doing, don't use their "miner", get a pure compilation of the newest T-rex or NBminer from their original repositories on GitHub for the best results and stability. As for the configuration for this specific use case, for each one there is a nice guide: