You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2020. It is now read-only.
The miner thread currently pushes work as hard as possible until all hashing tasks signal to be on a "wait for data transfer" stage.
Those signals are pooled in a single set used to sleep.
Unfortunately, this is not a valid operation when wait events come from different contexts. This causes wait to fail which in turn causes core usage go 100%.
A context is internal to each platform so this issue cannot be easily solved.
Possible solutions include:
Have a set of parallel threads waking up miner thread on first completion: relatively efficient but a lot of work for little benefit;
Just sleep for 1ms
clFinish
Latter 2 would need to be better investigated.
In the end, this does not seem to be something I want to support, much less implement soon.
The text was updated successfully, but these errors were encountered:
The miner thread currently pushes work as hard as possible until all hashing tasks signal to be on a "wait for data transfer" stage.
Those signals are pooled in a single set used to sleep.
Unfortunately, this is not a valid operation when wait events come from different contexts. This causes wait to fail which in turn causes core usage go 100%.
A context is internal to each platform so this issue cannot be easily solved.
Possible solutions include:
Latter 2 would need to be better investigated.
In the end, this does not seem to be something I want to support, much less implement soon.
The text was updated successfully, but these errors were encountered: