Skip to content

[GUI|MINE] update for override of max thread usage#975

Merged
codeofalltrades merged 1 commit intoVeil-Project:masterfrom
WetOne:MiningOverride
Apr 8, 2022
Merged

[GUI|MINE] update for override of max thread usage#975
codeofalltrades merged 1 commit intoVeil-Project:masterfrom
WetOne:MiningOverride

Conversation

@WetOne
Copy link
Collaborator

@WetOne WetOne commented Oct 22, 2021

Problem
Original implementation of the Mining Tab limits the user to only a number of threads equivalent to the number of cores the computer has. This is OK for SHA256 but should be allowed to be override for other algorithms.

Root Cause
No option for override

Solution
Implement the ability to override.

@Zannick Zannick added Component: GUI Primarily related to the display of the user interface Component: Miner Both PoW and PoS block creation Tag: PoW Related to Proof of Work consensus labels Oct 24, 2021
Copy link
Collaborator

@CaveSpectre11 CaveSpectre11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just noticed a couple more things; kicking back to re-review

Copy link
Collaborator

@CaveSpectre11 CaveSpectre11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also:
<string>Use your compter resources to create hashes looking for block solutions.</string>
has both a spelling error (compter) and an extra space between "hashes" and "looking"

Also; clicking "use max threads" gave me the 2^31 threads and filled in 'number of threads' with that number. I can enter a lower value into number of threads, but there's no way to get it to take, so I would have to click the - a couple billion times to get it to reduce.

@WetOne WetOne force-pushed the MiningOverride branch 2 times, most recently from 100203c to b133500 Compare November 5, 2021 03:59
@WetOne WetOne requested a review from CaveSpectre11 November 10, 2021 18:48
@CaveSpectre11 CaveSpectre11 added Tag: Waiting For Code Review Waiting for code review from a core developer and removed Tag: Waiting For Developer labels Nov 12, 2021
Copy link
Collaborator

@CaveSpectre11 CaveSpectre11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Still seeing spelling error (compter) and extra spaces between 'hashes looking' at the top of the page
  • Still seeing RandomX set 4 threads and with 4 CPU and 'exceeding recommended number of threads'
  • Since we can't edit the number of threads only up/down I think "use Max threads" should be disabled when it's setting it to INT_MAX

@WetOne
Copy link
Collaborator Author

WetOne commented Nov 12, 2021

I'm addressing the first two. I'm not quick clear on what you are asking for the last one. Are you saying that when the value is already at max that the "Use Max Threads" button should be disabled?

@WetOne
Copy link
Collaborator Author

WetOne commented Nov 12, 2021

Updated per comments.

@Zannick
Copy link
Collaborator

Zannick commented Nov 15, 2021

utACK 41888ea

@Zannick Zannick removed the request for review from CaveSpectre11 March 11, 2022 19:47
Copy link
Collaborator

@codeofalltrades codeofalltrades left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 41888ea

@codeofalltrades codeofalltrades added Code Review: Passed and removed Tag: Waiting For Code Review Waiting for code review from a core developer labels Apr 3, 2022
@codeofalltrades codeofalltrades merged commit ab85642 into Veil-Project:master Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Code Review: Passed Component: GUI Primarily related to the display of the user interface Component: Miner Both PoW and PoS block creation Tag: PoW Related to Proof of Work consensus

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants