livepeer
. Other miners that have been tested successfully
with livepeer
can be substituted for t-rex as well.
Note that regardless of the miner used, the VRAM available on your GPU will
affect the number of concurrent streams that can be transcoded while mining.
CUDA_VISIBLE_DEVICES
environment variable should be set with device IDs
of the GPUS you will be using before the MPS daemon is started, but it should
NOT be set before starting the miner and livepeer
--cuda-streams
, --cuda-block-size
and --cuda-grid-size
flags are used
to adjust the GPU workload. The best values to use for these flags will depend
on your GPU and whether you want lower hashrate and faster transcoding speed or
higher hashrate and lower transcoding speed.
If you are using t-rex, run t-rex with a flag to adjust mining intensity (other
flags to connect to a mining pool omitted):
-i
flag is used to adjust the mining intensity. Note that in testing, this
flag did not seem to provide very granual control over the GPU workload so
adjusting it to a level at which CUDA MPS could work led to a larger hashrate
drop which is why ethminer is recommended if you plan on using CUDA MPS.
livepeer
on the same machine as the miner and using the same GPU device
IDs as the miner with the -nvidia
flag
livepeer
will need to be stopped when the miner
re-generates the DAG to avoid transcoding issues and can be re-started when
DAG generation completes