Comment
Author: Admin | 2025-04-28
"OPTIONALNAMEHERE" -x 50 -jNotice that we also added the -j argument so that the client can have the JSON-RPC server enabled to communicate with the ethminer instances. Additionally we removed the mining related arguments since ethminer will now do the mining for us.For each of your GPUs execute a different ethminer instance:ethminer --no-precompute -G --opencl-device XXWhere XX is an index number corresponding to the openCL device you want the ethminer to use. In order to easily get a list of OpenCL devices you can execute ethminer --list-devices which willprovide a list of all devices OpenCL can detect, with also some additional information per device. Below is a sample output:[0] GeForce GTX 770 CL_DEVICE_TYPE: GPU CL_DEVICE_GLOBAL_MEM_SIZE: 4286345216 CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1071586304 CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024Finally the --no-precompute argument requests that the ethminers don't create the DAG of the next epoch ahead of time.BenchmarkingMining power tends to scale with memory bandwidth. Our implementation is written in OpenCL, which is typically supported better by AMD GPUs over NVidia. Empirical evidence confirms that AMD GPUs offer a better mining performance in terms of price than their NVidia counterparts. R9 290x appears to be the best card at present. To benchmark a single-device setup you can use ethminer in benchmarking mode through the -M option:ethminer -G -MIf you have many devices and you'll like to benchmark each individually, you can use the --opencl-device option similarly to the previous section:ethminer -G -M --opencl-device XXUse ethminer --list-devices to list possible numbers to substitute for the XX.
Add Comment