Skip to content
This repository was archived by the owner on Apr 24, 2022. It is now read-only.

Lack of options for benchmarking mode #231

Closed
Roaders opened this issue Aug 10, 2017 · 3 comments
Closed

Lack of options for benchmarking mode #231

Roaders opened this issue Aug 10, 2017 · 3 comments

Comments

@Roaders
Copy link

Roaders commented Aug 10, 2017

On my system I have the following devices listed:

Listing OpenCL devices.
FORMAT: [deviceID] deviceName
[0] Intel(R) HD Graphics 630
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 13663212340
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 2147483647
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
[1] GeForce GTX 1080 Ti
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 11811160064
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 2952790016
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024


Listing CUDA devices.
FORMAT: [deviceID] deviceName
[0] GeForce GTX 1080 Ti
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 11811160064

but when I run a benchmark it uses the on-motherboard intel gpu and not the GeForce GTX. Obviously I want to benchmark the GeForce...

I have tried using the options available for the mining mode:

ethminer -M -G --opencl --opencl-device 1

but this seems to have no effect.

We need a lot of the same options for benchmarking as we do for mining...

@EoD
Copy link
Contributor

EoD commented Aug 16, 2017

@Roaders I think you misunderstand the parameters here.

First of all, the parameter -G and --opencl are identical. No need to specify them both.
You do not have two different devices, but two different platforms here. I guess you want to specify --opencl-platform 1 instead of your device.

All in all: ethminer -G -M --opencl-platform 0 and ethminer -G -M --opencl-platform 1

I do agree, that the --list-devices in this case is misleading and might need some improvements to show platform and devices properly. Let's rename the bug to "Improve --list-devices to show opencl platform".

@DeadManWalkingTO
Copy link
Contributor

I think this issue can be closed.

@smurfy
Copy link
Collaborator

smurfy commented Feb 19, 2018

Fixed by #307

@smurfy smurfy closed this as completed Feb 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants