Skip to content

CrazyAra ignoring my UCI "Threads" option #35

Closed
@thomas-daniels

Description

@thomas-daniels

Because the CUDA version with cpu as Context did already work so far, I decided to try that already. I set the number of threads to use to one (same problem appears when picking 2 threads, didn't test for other values).

uci
setoption name Context value cpu
setoption name Threads value 1
isready
go movetime 5000

Screenshot from 2019-08-27 21-50-53

As confirmed with both htop and the System Monitor, CrazyAra takes up 100% of all my cores when thinking of a move, but that really shouldn't happen if I only specify one thread.

Metadata

Metadata

Assignees

Labels

questionFurther information is requested

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions